Bug #2157
closedMetacat Performance: Optimize Postgres and Tomcat...
0%
Description
There might be some options in Tomcat to speed things up a little bit. e.g.
Chris suggested about turning off autoloading of war files.
In Postgres.. From Matt's email...
It would be best to fit the whole postgres
image into memory so it need not be swapped to disk for queries.
Postgres needs to be configured to use the memory even if its on the
machine. Chris saw significant performance gains by upping the memory
for Postgres to 768MB. We have a much larger DB, so we probably want to
go higher. Ecoinfo2 has 2GB of RAM, which we should probably increase
to 4GB. New machines should have that much at least, but we run into
the 32bit limit so might need to consider moving to a 64bit os. Sid
should look at the memory size needed for the postgres image on ecoinfo2
to get an idea of how much we need.
Related issues
Updated by Saurabh Garg over 18 years ago
John made these changes on the new knb.msi machine.
But I am retargeting this to 1.7 instead of closing the bug, so that we can
review it again before the next release. Chris told me about how Postgres loses
a lot of time because of swapping between memory and disk. This can be fixed by
increasing RAM. Also I think heard that Postgres uses full table search even
when when index is specified based on the shared memory limit specified. Hence
there might be room for improvement here.
Updated by Saurabh Garg over 17 years ago
The current RAM specified for Tomat and Postgres in KNB:
Tomcat: 500 MB
Postgres: 760 MB
Updated by Jing Tao over 16 years ago
Here are current configuration in knb (total 8 G memory)
1) Set SHMMAX to 4,000,000,000
2) Assign Postgresql shared_buffer=400,000 (total is 400,000x8k=3.2G)
3) Assign 2048M to tomcat