Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   logbook db size causing very slow response, posted by eric wooten on Tue Dec 31 17:56:34 2002 
    icon3.gif   Re: logbook db size causing very slow response, posted by Etienne Van Caillie on Sat Jan 4 17:55:49 2003 
       icon2.gif   Re: logbook db size causing very slow response, posted by Stefan Ritt on Sat Jan 4 20:07:20 2003 
    icon2.gif   Re: logbook db size causing very slow response, posted by Stefan Ritt on Thu Jan 9 10:25:10 2003 
    icon2.gif   Re: logbook db size causing very slow response, posted by Stefan Ritt on Sat Jan 11 18:09:04 2003 
Message ID: 182     Entry time: Sat Jan 4 17:55:49 2003     In reply to: 181     Reply to this: 183
Icon: Idea  Author: Etienne Van Caillie  Author Email: etienne.vancaillie@mba.be 
Category: Comment  OS:   ELOG Version:  
Subject: Re: logbook db size causing very slow response 
> Was wondering if there were any tweaks/suggestions for improving the 
> logbooks responsiviness.  Our logbook was started 31 July 01.  Since that 
> time we have went from 1 logbook to 4 logbooks.  Logbook 1 having 2651 
> entries, logbook 2 having 300 entries, and the last 2 are new logbooks, so 
> only a few entries.
> 
> When user launches the logbook website, it takes considerable time to bring 
> the site up.  It seems to be directly related to the number of entries in 
> the logbook.  If I set up a dummy site with a couple logbooks and only a 
> few entries, the logbook is very fast coming up as well as saving entries.
> 
> Another thing that seems to slow the site down, is the number of users in 
> the elog notification list (those who've subscribed).  When you save a log 
> entry, it takes around 30sec or longer for it to actually complete the 
> save.  If I remove the list of users from the notification list and just 
> have a few, the save is very fast.
> 
> 
> Thanks in advance,
> 
> Eric

2600 entries is too much for this application as it load the all files 
in computer memory
expand the server memory
Are you running on linux or Windows ? I suggest linux (faster)
We are working on the C source to move all data from flat to database like 
SQL or mysql
when a parameter flag like 'status' = "OK" for instance
I suggest also to split in several logbook
but this is depend on your 'ELOG' parametrisation and logics

If your data are not 'sensitive' I can check on my linux server

Etienne
ELOG V3.1.5-fe60aaf