Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   HW Requirements to run elog / Performance issues running on ARM, posted by Tim Thiel on Wed May 9 21:48:42 2012 elogd-001.cfg
    icon2.gif   Re: HW Requirements to run elog / Performance issues running on ARM, posted by Yoshio Imai on Thu May 10 15:34:39 2012 
       icon2.gif   Re: HW Requirements to run elog / Performance issues running on ARM, posted by Tim Thiel on Thu May 10 16:35:50 2012 
          icon2.gif   Re: HW Requirements to run elog / Performance issues running on ARM, posted by Stefan Ritt on Fri May 11 13:20:35 2012 
             icon2.gif   Re: HW Requirements to run elog / Performance issues running on ARM, posted by Tim Thiel on Mon May 14 22:19:50 2012 
                icon2.gif   Re: HW Requirements to run elog / Performance issues running on ARM, posted by Stefan Ritt on Tue May 15 08:35:16 2012 
Message ID: 67270     Entry time: Thu May 10 16:35:50 2012     In reply to: 67269     Reply to this: 67271
Icon: Reply  Author: Tim Thiel  Author Email: tt2005@thieleng.com 
Category: Question  OS: Linux  ELOG Version: 2.9.0 
Subject: Re: HW Requirements to run elog / Performance issues running on ARM 

Yoshio Imai wrote:

Hi!

Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.

Yoshio

 Yoshio,

Thanks for the suggestion.

We have actually tried running the elog server with a very minimal set of attributes, all of which were human entries, and still had response times that were entirely unacceptable.  So, unfortunately this path won't solve all our issues.

tt

 

ELOG V3.1.5-3fb85fa6