Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon6.gif   testing for the limit of the elog database , posted by Arno Teunisse on Sat Oct 6 15:39:12 2007 
    icon2.gif   Re: testing for the limit of the elog database , posted by Stefan Ritt on Sat Oct 6 15:44:51 2007 
       icon2.gif   Re: testing for the limit of the elog database , posted by Arno Teunisse on Sat Oct 6 15:56:13 2007 
          icon2.gif   Re: testing for the limit of the elog database , posted by Stefan Ritt on Sat Oct 6 16:11:50 2007 
Message ID: 2322     Entry time: Sat Oct 6 15:39:12 2007     Reply to this: 2323
Icon: Cool  Author: Arno Teunisse  Author Email: A.Teeling3@chello.nl 
Category: Question  OS: Windows  ELOG Version: 2.6.5-1890 
Subject: testing for the limit of the elog database  
Hello

To test elog i created a very large databasefile ( 071006a.log = 39MB ) via an import.
Nothing special. At the import I already got a message to increase "Max content length" to 22420822 in the global section. Below is the what i've done. There are no attachments involved, as you can see.
[global]
port = 80;
Max content length = 22420822
[DAP]
Theme = default
Attributes=Klant,Doc
Quick filter = Klant

So there are only 2 user defined fields in the database.
Everything works ......... but terrible slow : is there a rule of thumb for the size of the database ?
ELOG V3.1.5-2eba886