If the *LOWMEM 2 commands don't help, then you will probably need to use the *LOWMEM 3 commands. Particularly on the items that have the most unique values.
You should also look at that data and see if there are ways you can save space by reducing what is counted. For example, if each of your users is given a unique session id that is stored in the request string, then this will make virtually every request a unique item and quickly fill up the hashtable (and your memory). In such a case you can use ALIAS commands to make similar items the same and help reduce what is counted. This also hold for referrers, especially those from advertising sources.
If you have gotten to a point where the amount of data that you are processing has vastly outgrown your available memory, then you really need to step back and ask what information your are actually looking for. Sometimes it seems like a good idea to be able to create cumulative reports from the beginning of time, but in general, you can get by with monthly reports and compare monthly activity in a side-by-side fashion. This also helps highlight trends (periodic and seasonal) that you may not be able to see in a cumulative report.
-- Jeremy Wadsack Seven Simple Machines
Michael Simmons wrote:
Hi Duke,
I've tried changing these settings but still no joy. Here are the settings I'm using:
FILELOWMEM 2 HOSTLOWMEM 2 BROWLOWMEM 2 REFLOWMEM 2 USERLOWMEM 2 VHOSTLOWMEM 2
Thanks in advance for your help.
Mike.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Duke Hillard Sent: 08 September 2004 19:24 To: Support for analog web log analyzer Subject: Re: [analog-help] analog bombing out halfway through analysis
Have you seen "Coping with low memory" at "http://www.analog.cx/docs/lowmem.html";?
-- Duke
Michael Simmons wrote:
3MBHi,
I receive the following error message when running analog:
Fatal Error: Ran out of memeory: cannot continue: exiting
I am running analog on a box with over 2GB ram. The logfiles range from
to 50MB and there about 168 logfiles per box and 12 boxes. It bombs out onstarts
the 3rd box - it gets to around the same sort of range and the memory
ramping up until it drops and then falls over. I have tried taking thein
logfiles out that it fails on, but it then just fails on the next logfile
the list.
I'd be very grateful for some ideas.
Cheers,
Mike.
-------------------------- Michael Simmons Support Engineer On Demand Distribution PLC
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------
+------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
