Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 16 16:20:06 2006 
    icon2.gif   Re: Problem with large entry size, posted by Stefan Ritt on Mon Oct 16 16:53:43 2006 
       icon2.gif   Re: Problem with large entry size, posted by Stefan Ritt on Mon Oct 16 17:18:58 2006 
          icon2.gif   Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 16 17:32:58 2006 
       icon2.gif   Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:39:29 2006 
          icon2.gif   Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 17 14:42:58 2006 
             icon2.gif   Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:47:53 2006 
             icon2.gif   Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 23 12:53:08 2006 
                icon2.gif   Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 24 21:58:54 2006 
                   icon2.gif   Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Thu Nov 2 10:14:11 2006 
                      icon2.gif   Re: Problem with large entry size, posted by Stefan Ritt on Thu Nov 9 21:22:27 2006 
Message ID: 1992     Entry time: Mon Oct 16 16:53:43 2006     In reply to: 1991     Reply to this: 1993   2003
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS:   ELOG Version:  
Subject: Re: Problem with large entry size 

Dimitrios Tsirigkas wrote:
I have posted an entry of approximately a thousand lines (ten thousand words). Posting it took some time, which is logical to a certain degree. However, whenever a user asks for "Full" view of the logbook, the page takes around two minutes to load and the CPU usage on the elog server goes to beyond 90% for all this time. Is this to be expected for an entry of that size or is there something going wrong here?


The problem lies in the ELCode parsing. When you post an entry in ELCode form, the elogd server has to parse every word to see if it's any of the ELcode tags. This is right now implemented in a kind of poor way, such that it takes very long for long entries. I will work to optimize that. In the meantime, it will help if you post such long entries just in "plain" form.

- Stefan
ELOG V3.1.5-fe60aaf