Difference between revisions of "Template:SS-GRAPHS"
Jump to navigation
Jump to search
| (8 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
|- align="center" | |- align="center" | ||
|width="50%"| | |width="50%"| | ||
| − | All our tweaks and | + | All our tweaks and [[SUNScholar/Optimisations|optimisations]] seem to be working. |
The load dropped when we started using "authbind" for Tomcat thereby eliminating the need for the Apache "mod_jk" module, which was creating extra processing overhead. | The load dropped when we started using "authbind" for Tomcat thereby eliminating the need for the Apache "mod_jk" module, which was creating extra processing overhead. | ||
| − | [[File:Sunscholar-load-year.png | + | [[File:Sunscholar-load-year.png]] |
| | | | ||
| − | Looks like we have enough disk space for the next 3yrs at least at our current rate of submissions. | + | Looks like we have enough disk space in the '''/home''' partition for the next 3yrs at least, at our current rate of submissions. The '''/var''' partition which holds the database was reduced in size by tweaking the bitstream checker properties and then running a full database vacuum. |
| − | [[File:Sunscholar-disk-usage-year.png | + | [[File:Sunscholar-disk-usage-year.png]] |
|- align="center" | |- align="center" | ||
| | | | ||
We have more than enough compute muscle. | We have more than enough compute muscle. | ||
| − | [[File:Sunscholar-cpu-year.png | + | [[File:Sunscholar-cpu-year.png]] |
| | | | ||
| − | Our memory usage stabilised when we stopped using the JSPUI. | + | Our memory usage stabilised when we stopped using the JSPUI. However after the upgrade to DSpace 1.8.2 and enabling discovery we are back to a memory intensive system. |
| − | [[File:Sunscholar-memory-year.png | + | [[File:Sunscholar-memory-year.png]] |
|} | |} | ||
Latest revision as of 09:58, 14 June 2013
|
All our tweaks and optimisations seem to be working. The load dropped when we started using "authbind" for Tomcat thereby eliminating the need for the Apache "mod_jk" module, which was creating extra processing overhead.
|
Looks like we have enough disk space in the /home partition for the next 3yrs at least, at our current rate of submissions. The /var partition which holds the database was reduced in size by tweaking the bitstream checker properties and then running a full database vacuum.
|
|
We have more than enough compute muscle.
|
Our memory usage stabilised when we stopped using the JSPUI. However after the upgrade to DSpace 1.8.2 and enabling discovery we are back to a memory intensive system.
|
