> 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

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

I have some problem with email notification
for some logbooks I would like to notify only to specific adress
I try
Email All = adress1, adress2

Elog send well at 'adress1' and 'adress2' 
but also to all of other users ?
how to restric these only to 'adress1 and adress2 ?

is it possible to notify according to attribue value like

Attributes = Test1, Test2
Email All = $Test1

or concatenation of  $Test1 + '@mba.be' for example

Thanks

this is a wonderfull tools !
to improve documentation : true example are missing too much 'theorie'
but when I'm finish I'll put true sample on the net 

> I checked your elogd.cfg: The flag is called "Expand default" not "Expand" as 
> you had it. With "Expand default = 0" it works fine. Just RTFM...

i could probably recite the manual from memory :/ i wouldn't ask if i wasn't confused about something.

i thought the 'default' word was explaining what the default was for the 'expand' flag, not an actual part of the flag. 

> > i have expand flag set to 0 but it doesn't seem to be working...
> 
> It workes here flawlessly. Can you double check the spelling etc. If 
> everything is ok, can you send me your elogd.cfg for analysis?
> 
> - Stefan

I checked your elogd.cfg: The flag is called "Expand default" not "Expand" as 
you had it. With "Expand default = 0" it works fine. Just RTFM...

- Stefan 

> i have expand flag set to 0 but it doesn't seem to be working...

It workes here flawlessly. Can you double check the spelling etc. If 
everything is ok, can you send me your elogd.cfg for analysis?

- Stefan

i have expand flag set to 0 but it doesn't seem to be working...

i can expand and collapse via the links, or if i make sure the url includes it.

> This feature has been added in Version 2.2.4 which has been released today. 
> Use the "collase" button.

> This feature has been added in Version 2.2.4 as well. Use "line as link = 1" 
> in elogd.cfg

thanks. that was quick :)