Slow performance, posted by Alan Grant on Tue Jun 28 18:53:50 2022
|
We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.
Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this? |
Re: Slow performance, posted by Andreas Luedeke on Sat Jul 2 14:39:41 2022
|
We have 68 logbooks and currently 60 GB data total. We run it as well on a VM, in our case with 8GB RAM.
The speed of ELOG is mostly given by the filesystem: when we had AFS it was very slow. With NFS it was better. But we now use a local disk on the VM: that is much better.
If you want to have the best performance (upload of large files can still slow down all users) then I would recomment local SSD for the file system of elogd.
You might talk to your system administrator: they can likely provide a local SSD on the VM server host.
| Alan Grant wrote: |
|
We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.
Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this?
|
|
Re: If a Required Attribute starts with a number – No CKEditor, posted by Andreas Luedeke on Fri Dec 11 14:30:10 2015
|
Hi David,
I can confirm a bug: changing the encoding does not work if you have a required attribute starting with a digit. The following minimal config reproduces the bug:
[global]
Default encoding = 1
[test]
Attributes = 7SWM
Options 7SWM = Name
Required Attributes = 7SWM
Whatever you choose as a default encoding you'll be stuck with. If you remove the "Required Attributes" it works again.
The workaround is very simple: do not use any attributes that do start with a digit :-)
Cheers, Andreas
| David Dunne wrote: |
| Hello, Is the below an issue or am I doing something incorrectly? Creating an attribute starting with a number and then including that attribute in the Required Attribute list prevents access to the CKEditior. This appears to be the case at least with FreeBSD (10.2 Rel) using Elog V3.1.0 and Windows 7 with Elog V3.1.1-3f311c5. The problem can be recreated using the Elog supplied sample config and adding the necessary attribute, sample config showing below. While attribute 7SWM is part of the Required Attributes the CKEditor fails to appear, remove 7SWM from the Required Attributes list and the CKEditor returns. [global] port = 8080 [demo] Theme = default Comment = General Linux Tips & Tricks Attributes = Author, Type, Category, Subject, 7SWM Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other Options Category = General, Hardware, Software, Network, Other Options 7SWM = Name-1, Name-2, Name-3 Extendable Options = Category Required Attributes = Author, Type, 7SWM Page Title = ELOG - $subject Reverse sort = 1 Quick filter = Date, Type Thank you, David Dunne |
|
Hilight code, posted by Daniel Sajdyk on Tue Sep 6 13:29:03 2016
|
Hello :)
Is there any way to highlight code (for example php, SQL) in logs entries?
Best Regards
Daniel Sajdyk |
|
Highlight code?, posted by Daniel Sajdyk on Tue Sep 6 13:35:05 2016
|
Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk |
|
Re: Highlight code?, posted by Stefan Ritt on Tue Sep 6 13:41:32 2016
|
You can manually highlight code, but there is no automatic language parser.
| Daniel Sajdyk wrote: |
|
Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk
|
|
|
Re: Highlight code?, posted by Daniel Sajdyk on Tue Sep 6 13:45:55 2016
|
I thought so.
One more question :) I want manually add that parser (https://highlightjs.org), but I'm newby in that and don't know where ....
I know that downloaded hightlight pack I must put into folder scripts, but where to add this line:
<script>hljs.initHighlightingOnLoad();</script>
| Stefan Ritt wrote: |
|
You can manually highlight code, but there is no automatic language parser.
| Daniel Sajdyk wrote: |
|
Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk
|
|
|
|
Re: Highlight code?, posted by Stefan Ritt on Tue Sep 6 14:02:56 2016
|
I did not know about highlight.js . You can put it into any elog page with "Bottom text = ...". I tried it for this forum and put in some C code:
#include <stdio.h>
int main()
{
// printf() displays the string inside quotation
printf("C Programming");
return 0;
}
Seems like this works nicely. Thanks for that hint.
| Daniel Sajdyk wrote: |
|
I thought so.
One more question :) I want manually add that parser (https://highlightjs.org), but I'm newby in that and don't know where ....
I know that downloaded hightlight pack I must put into folder scripts, but where to add this line:
<script>hljs.initHighlightingOnLoad();</script>
| Stefan Ritt wrote: |
|
You can manually highlight code, but there is no automatic language parser.
| Daniel Sajdyk wrote: |
|
Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk
|
|
|
|