Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 16 16:20:06 2006
|
Hi Stefan,
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?
Thanks,
Dimitris |
Re: Problem with large entry size, posted by Stefan Ritt on Mon Oct 16 16:53:43 2006
|
| 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 |
|
Re: Problem with large entry size, posted by Stefan Ritt on Mon Oct 16 17:18:58 2006
|
I improved the performance by some factor in SVN revision 1733. Can you give it a try and report your speed improvement? Depending on the result, I can probably do even a bit better with some more effort.
- Stefan |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 16 17:32:58 2006
|
| Stefan Ritt wrote: | I improved the performance by some factor in SVN revision 1733. Can you give it a try and report your speed improvement? Depending on the result, I can probably do even a bit better with some more effort.
- Stefan |
Dear Stefan,
Thank you for your quick reply. I will install the new version and I will let you know as soon soon as possible.
Best,
Dimitris |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:39:29 2006
|
| Stefan Ritt wrote: |
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 |
Hi again,
I was wondering what is the cleanest way of changing old entries already submitted in ELCode into plain text. If I do not include ELCode in the allowed encodings does this apply to already submitted entries as well or will they still be treated as ELCode?
Thanks,
Dimitris |
|
Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 17 14:42:58 2006
|
| Dimitrios Tsirigkas wrote: | | I was wondering what is the cleanest way of changing old entries already submitted in ELCode into plain text. If I do not include ELCode in the allowed encodings does this apply to already submitted entries as well or will they still be treated as ELCode? |
The encoding is stored as an "invisible" attribute in each entry. You can change it in two ways:
1) Select each entry, click "edit", change the encoding with the radio buttons at the bottom and submit it again
2) Go and edit directly the xxxxxxa.log files in your logbook directory. You will see in those files something like
Encoding: ELCode
and you can change it with an editor to
Encoding: plain
Afterwards you have to restart the elogd daemon.
Did you try the new version, would be interesting to see if it's any better... |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:47:53 2006
|
Thanks Stefan,
| Stefan Ritt wrote: | | Did you try the new version, would be interesting to see if it's any better... |
I didn't find the time to try it yet but I will do that later today. I will keep you posted - more soon.
Cheers,
Dimitris |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 23 12:53:08 2006
|
Hi Stefan,
A lot of performance-related trouble for us comes from the ability of users to click on "All" and display thousands of entries on the same page. Is there a way to disable that? Even if the ELCode parsing performance of Elog increases greatly, the combination of "Full" mode and "All" will still cause trouble, will it not?
Thanks,
Dimitris |