This is very strange.
We are know about the FilePageStore.storePage performance issues and
johan is working on optimizing that.
but CompressedPackageResource shouldn't take 30%. Definitely not. caches
the resource so the serving should be immediate. Unless your machine
runs out of memory, in that case the cache is evicted.
I'm not sure but i think there was a memory leak in 1.x lately, are you
sure you're using the latest version?
What's the configuration of your server?
Btw. You can try to use HttpSessionStore to see if it makes serving
pages faster
(in your application class
protected ISessionStore newSessionStore() {
return new HttpSessionStore();
}
)
-Matej
Andrew Klochkov wrote:
> forgot to mention the version - we use wicket 1.3
>
> Andrew Klochkov wrote:
>> Hi
>>
>> Recently we launched some simple webapp written in wicket, but
>> performance is obviously low. Even simple pages are being loaded too slow.
>> I tried to dig into it using profiler and found out that wicket takes
>> 67% of CPU to work with file system. Main points of low performance are:
>>
>> 1. wicket.protocol.http.FilePageStore.storePage eats 25% of CPU
>> 2. getting resources using CompressedPackageResource eats 30% of CPU
>>
>> How can we improve it? Why does wicket save all the pages in files, why
>> not to use http sessions?
>> And what can be done with resources? I guess the browser doesn't cache
>> them and it takes to long time to get them from jars.
>>
>>
>
>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
