[MAGNOLIA-2507] performance issues with JBoss and behavior of the cache Created: 11/Dec/08 Updated: 27/Nov/13 Resolved: 27/Nov/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | cache |
| Affects Version/s: | 3.6.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Juan Carlos, Antonio | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
server Linux with: |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
The 4 tests are as follows:
The Public's cache is set to come by default in the distribution with Tomcat. We find the following in the different tests: Try-TOMCAT and without parameters Try-JBoss and without parameters In general we see the evidence with JBoss are worse than Tomcat, and it appears that page to update any impact on the performance of others that have not been touched. We believe that this should not be so. Latest tests with Java 1.6 platform in Magnolia 3.6.1 + JBoss + MySQL in the file prueba_081203_JBoss_jdk16_SinParametros-Tiempo Respuesta.pdf are with JBOSS with the template without parameters and we can see: According to the evidence seems to be that whenever a page is updated on amending the entire cache of Public. in the file prueba_081203_JBoss_jdk16-ConParametros-Tiempo Respuesta.pdf are with JBOSS with the template with parameters for the language es_ES and the language en_US, language ca_ES is the default language of the template and do not use the parameter. We can see: With the upgrade of java has earned enough respect to the previous tests, it looks like there are no jumps of 5, 8 seconds before ox if passed and randomly in all languages, and this does not happen now, all the times Now follow the same pattern. In the previous tests can also be seen as performance is better than Tomcat with JBoss (with the same machine, same MySQL and the same values of memory). With these and previous tests can give us a logical explanation of what is happening, whether the cache should behave like it or not, and if the JBoss we should give better results than the Tomcat. |