[imp] Re: [horde] Who is online?

[Gary Smith]

The database is indeed MySQL what most of the people around me are using.  As for the generalized topic (which I know is kinda getting off topic) my point was feature rich can quickly equate to slow using any RDBMS.  I know that knowing who is currently online (which may not be a true statement at any point in time) is a feature that many systems seem to implement more frequently. 
 
I was merely raising the point that many of these items seem important, they get coded, and then implemented and finally they are used for the first couple weeks then no one every used them again.  But in the background the process cycles are being wasted away logging this information to file or database. 
 
Now, back onto the original topic
 
Another point (geared towards the original author of this thread) is that "who's online" is not an accurate representation of what's happening.  is typically means "who has been online" during the criteria timeframe we specified.Thus, the concept of purging a file for sometime of reporting seems to be more valid then logging it to a db.  Here's where the fundamental problem lies.  If I login and check my email and them shutdown IE you still think I'm online (unless you are somehow requiring persistent connections).  Most of the applications say any user within the last x (usually being 15 or 30) is considered to be online if they have accessed the system.
 
Just my $0.02 :)
 
Gary Smith
 
 

	-----Original Message----- 
	From: Jan Schneider [mailto:jan at horde.org] 
	Sent: Mon 9/8/2003 1:45 AM 
	To: imp at lists.horde.org 
	Cc: 
	Subject: RE: [imp] Re: [horde] Who is online?
	
	

	Zitat von Lord Apollyon <implist at paypc.com>:
	
	> > We found that by removing things like "who's online"
	> > tracking information out of programs like phpnuke we get a good amount
	> of
	> > CPU back under normal usages (300k hit's/day).
	>
	> Let me guess, he's using mySQL.  mySQL is the Open Source Posterchild of
	> the
	> Day, but it's not a very fast database when you start to really lean on
	> it.
	>  One area of "lean" it's not good at handling is extensive UPDATE/INSERTs
	> on
	> read-active tables.  Notice how many language constructs they've created
	> to
	> try to minimise the inevitable - UPDATE DELAYED, PRIORITY, etc.
	
	But of course this (being one of the fastest out there) RDBMS has support
	for in-memory HEAP tables that are the ideal table type for session
	handlers and live logging/statistics.
	
	Jan.
	
	--
	http://www.horde.org - The Horde Project
	http://www.ammma.de - discover your knowledge
	http://www.tip4all.de - Deine private Tippgemeinschaft
	
	--
	IMP mailing list
	Frequently Asked Questions: http://horde.org/faq/
	To unsubscribe, mail: imp-unsubscribe at lists.horde.org