Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B24710ADF for ; Wed, 26 Feb 2014 16:30:41 +0000 (UTC) Received: (qmail 92641 invoked by uid 500); 26 Feb 2014 16:30:39 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 92582 invoked by uid 500); 26 Feb 2014 16:30:34 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 92516 invoked by uid 99); 26 Feb 2014 16:30:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Feb 2014 16:30:32 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Feb 2014 16:30:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=Jdma+ya/VaRD5KPH0cVb7sRGFB0LaCikCKf0a0JjkAE=; b=puZSTSnppW9d7RA7Evru24T0be8JR/nKlQZ62WZfI5nlAPnIzAL30S19y3OcReUYFtqGUlP1E/KRFQIcmVHO3TQ2/btgAXQiAGst8gmHRnO/sw3bbKQkWdnHedY+PKKgItPovmQw3hDhOloCxKQbyW3l00MVGERvlPQviUdHAxU=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-4.v29.ch3.sourceforge.com) by sfs-alluradaemon-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WIhMy-0007dy-Uu for allura-dev@incubator.apache.org; Wed, 26 Feb 2014 16:30:05 +0000 Content-Type: multipart/related; boundary="===============2944299524617590926==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Dave Brondsema" Reply-To: "Ticket 7223" <7223@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #7223 Config option to disable userstats tracking Message-ID: <530e166f7929e56590eeacda.tickets@allura.p.sourceforge.net> Date: Wed, 26 Feb 2014 16:30:04 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============2944299524617590926== Content-Type: multipart/alternative; boundary="===============4030938407591900822==" MIME-Version: 1.0 --===============4030938407591900822== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit --- ** [tickets:#7223] Config option to disable userstats tracking** **Status:** open **Labels:** performance **Created:** Wed Feb 26, 2014 04:29 PM UTC by Dave Brondsema **Last Updated:** Wed Feb 26, 2014 04:29 PM UTC **Owner:** nobody Userstats should have an option to disable tracking, for forges that don't want to track or are have users with enough activity that the current userstats logic doesn't scale well. Example, one record that is about 5MB large, mostly contained in ".lastmonth.messages" but other parts of the data structure can also be very large. ~~~~ forge:SECONDARY> Object.bsonsize(db.userstats.findOne({user_id: db.user.findOne({username:'brondsem'})._id })) 5018300 forge:SECONDARY> Object.bsonsize(db.userstats.findOne({user_id: db.user.findOne({username:'brondsem'})._id }).lastmonth.messages) 5005740 forge:SECONDARY> db.userstats.findOne({user_id: db.user.findOne({username:'brondsem'})._id }).lastmonth.messages.length 52178 ~~~~ --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============4030938407591900822== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

[tickets:#7223] Config option to disable userstats tracking

Status: open
Labels: performance
Created: Wed Feb 26, 2014 04:29 PM UTC by Dave Brondsema
Last Updated: Wed Feb 26, 2014 04:29 PM UTC
Owner: nobody

Userstats should have an option to disable tracking, for forges that don't want to track or are have users with enough activity that the current userstats logic doesn't scale well.

Example, one record that is about 5MB large, mostly contained in ".lastmonth.messages" but other parts of the data structure can also be very large.

forge:SECONDARY> Object.bsonsize(db.userstats.findOne({user_id: db.user.findOne({username:'brondsem'})._id }))
5018300
forge:SECONDARY> Object.bsonsize(db.userstats.findOne({user_id: db.user.findOne({username:'brondsem'})._id }).lastmonth.messages)
5005740
forge:SECONDARY> db.userstats.findOne({user_id: db.user.findOne({username:'brondsem'})._id }).lastmonth.messages.length
52178

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============4030938407591900822==-- --===============2944299524617590926==--