Resource Menu

posted by Sebastien Jourdain at Aug 29, 2007 2:45 PM
Vacuuming the database every day is a good thing to do. Anyway.


posted by Rüdiger Lincke at Aug 29, 2007 2:07 PM
Hi Seb, thanks again for your fast answers.

Interesting to know that its because of the improved security checks. I guess I can live with it. Eventhough the response times seem longer, the platform is table.

I will try to vacuum and reindex the database tonight. Yet I guess it does not help much, since I did with the migration a dump/restore. So the database should be in good shape

I will observe how it performes under load starting next week. If necessary I will try to upgrade the hardware.

Also lets see what LS 2.3 can do I am looking forward to it.

posted by Sebastien Jourdain at Aug 29, 2007 1:27 PM
Don't worry Rüdiger,

It's NOT your hardware.

Did you vaccumed your database ?

The explanation might sounds strange if I say that's an improvement but it is.

The performance issue comes from the security check :

  • LSC 1.5 was working like a Unix file system regarding the management of the security. I mean, when you can read a node, you are able to list all its children even if you don't have to read one of them.
  • LSC 2.x integrates the security management of LibreSource Enterprise, where you are not able to see a resource if you don't have the right to see it.
Basically if you have a huge amount of children and you are using the macro children to list them, then it may take a while. But if you use static content then it will be quicker.

LibreSource 2.3 reduce the cost of this security check.

To get you an idea of our hardware and our configuration :

  • Core 2 Duo + 3Go RAM
  • 6 Jonas/LibreSource (LSE 2.3)
  • 300Mo / Libresource
  • 1 Postgres 8.x
posted by Rüdiger Lincke at Aug 29, 2007 1:04 PM
Hello just a question about the performance of LibreSource.

Its maybe subjective, but version 2.2 feels a bit slower than 1.5.

Refreshing a page (F5 in IE) shows 600+ ms to display the page. If I refresh 10x (pressing F5 quickly in succession) it shows something above 4000 ms. Keeping F5 pressed for a few seconds results in a value of 41000+ ms when the page is loaded, and the CPU of the server I got LS running on is on nearly 100%.

I am the only user currently, and I am a bit worried, how this looks, if soon 10+ people are working on LS at the same time.

Is this normal behaviour regarding my hardware? What is a good value for loading a page? I see the loads in 60+ ms. About 10x faster as on my system.

What is the maximum number of users LS can handle at the same time?

Are there any tweaks I can use to improve performance?

My server runes Linux, with a P4, 2.4 GHz and 2.5 GB RAM. Postgres 8.0.13 is running on the same machine.

What I experience is it due to my hardware is maybe to slow, or is a configuration issue?

Thank you for any comments, suggestions, or experience reports.