9 Replies Latest reply on Feb 6, 2006 9:24 AM by pmn92

    portal management response time > 3 secs !

    pmn92 Novice

      Is there any reason that would explain why the response time is between 2 and 4 seconds, sometimes more ? It must be something, right?

      great product anyway...

        • 1. Re: portal management response time > 3 secs !
          Roy Russo Master

          Do you have a lot of nodes in the portal tree? Or is this a bare install?

          • 2. Re: portal management response time > 3 secs !
            pmn92 Novice

            Not many for now:
            . a portal
            . 36 pages
            . 108 windows / portlet instances

            This will grow by 5 or 6 times

            And in addition, multiple virtual portal like this one will coreside...

            Thanks

            Philippe

            • 3. Re: portal management response time > 3 secs !
              pmn92 Novice

              I tried with 2.2.1 bundled, changed to postgresql, creating a new database.

              Once the portal is started, the gui launched and connected under admin.

              clicking back and forth on "management" tab and on "default" tab takes between 3 to 6 seconds. It is extremely slow.

              Compared to that my portlet are very fast, even in debug mode with a lot of HQL traces ;-)

              It must be something...right?

              • 4. Re: portal management response time > 3 secs !
                Roy Russo Master

                I am not seeing slow reponse times between pages, but I just recently got a new laptop for dev.

                P 2.14
                2GB

                I am also using hypersonic right now, until I get around to installing PGres, etc...

                • 5. Re: portal management response time > 3 secs !
                  pmn92 Novice

                  Thanks for the answer.

                  I am still wondering why... I have an intel P IV Dual Core 3 GHz and 4 GB RAM - am running Windows 2003, and the jvm is 1.4.2.

                  The server and the client run on the same machine (localhost port 8080)

                  If I find out what it is, I will let you know...

                  • 6. Re: portal management response time > 3 secs !
                    Viet Master

                    I have a P200 MMX it's fast

                    • 7. Re: portal management response time > 3 secs !
                      pmn92 Novice

                      I have a lot of those :

                      2006-02-06 01:03:41,919 WARN [org.hibernate.cache.ReadWriteCache] (org.hibernate.cache.ReadWriteCache.handleLockExpiry(ReadWriteCache.java:214)) An item was expired by the cache while it was locked (increase your cache timeout): org.jboss.portal.core.impl.model.portal.ObjectNode.children#412
                      2006-02-06 01:03:41,919 DEBUG [org.hibernate.cache.UpdateTimestampsCache] (org.hibernate.cache.UpdateTimestampsCache.invalidate(UpdateTimestampsCache.java:64)) Invalidating space [JBP_OBJECT_NODE], timestamp: 4666098572980225
                      2006-02-06 01:03:41,919 DEBUG [org.hibernate.cache.ReadWriteCache] (org.hibernate.cache.ReadWriteCache.release(ReadWriteCache.java:195)) Releasing: org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413
                      2006-02-06 01:03:41,919 DEBUG [org.hibernate.cache.EhCache] (org.hibernate.cache.EhCache.get(EhCache.java:104)) key: org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413
                      2006-02-06 01:03:41,919 DEBUG [net.sf.ehcache.store.MemoryStore] (net.sf.ehcache.store.MemoryStore.get(MemoryStore.java:201)) org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredPropertiesCache: MemoryStore hit for org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413
                      2006-02-06 01:03:41,919 DEBUG [net.sf.ehcache.Cache] (net.sf.ehcache.Cache.isExpired(Cache.java:878)) org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413 now: 1139184221919
                      2006-02-06 01:03:41,919 DEBUG [net.sf.ehcache.Cache] (net.sf.ehcache.Cache.isExpired(Cache.java:879)) org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413 Creation Time: 1139184221825 Next To Last Access Time: 0
                      2006-02-06 01:03:41,919 DEBUG [net.sf.ehcache.Cache] (net.sf.ehcache.Cache.isExpired(Cache.java:881)) org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413 mostRecentTime: 1139184221825
                      2006-02-06 01:03:41,919 DEBUG [net.sf.ehcache.Cache] (net.sf.ehcache.Cache.isExpired(Cache.java:882)) org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413 Age to Idle: 120000 Age Idled: 94
                      2006-02-06 01:03:41,935 DEBUG [net.sf.ehcache.Cache] (net.sf.ehcache.Cache.isExpired(Cache.java:906)) org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties: Is element with key org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413 expired?: false
                      2006-02-06 01:03:41,935 WARN [org.hibernate.cache.ReadWriteCache] (org.hibernate.cache.ReadWriteCache.handleLockExpiry(ReadWriteCache.java:214)) An item was expired by the cache while it was locked (increase your cache timeout): org.jboss.portal.core.impl.model.portal.PortalObjectImpl.declaredProperties#413
                      2006-02-06 01:03:41,935 DEBUG [org.hibernate.cache.UpdateTimestampsCache] (org.hibernate.cache.UpdateTimestampsCache.invalidate(UpdateTimestampsCache.java:64)) Invalidating space [JBP_PORTAL_OBJECT_PROPS], timestamp: 4666098573045761
                      2006-02-06 01:03:41,935 DEBUG [org.hibernate.cache.ReadWriteCache] (org.hibernate.cache.ReadWriteCache.release(ReadWriteCache.java:195)) Releasing: org.jboss.portal.core.impl.model.portal.ObjectNode.children#414
                      2006-02-06 01:03:41,935 DEBUG [org.hibernate.cache.EhCache] (org.hibernate.cache.EhCache.get(EhCache.java:104)) key: org.jboss.portal.core.impl.model.portal.ObjectNode.children#414
                      2006-02-06 01:03:41,935 DEBUG [net.sf.ehcache.store.MemoryStore] (net.sf.ehcache.store.MemoryStore.get(MemoryStore.java:204)) org.jboss.portal.core.impl.model.portal.ObjectNode.childrenCache: MemoryStore miss for org.jboss.portal.core.impl.model.portal.ObjectNode.children#414
                      2006-02-06 01:03:41,935 DEBUG [net.sf.ehcache.Cache] (net.sf.ehcache.Cache.get(Cache.java:370)) org.jboss.portal.core.impl.model.portal.ObjectNode.children cache - Miss
                      2006-02-06 01:03:41,935 DEBUG [org.hibernate.cache.EhCache] (org.hibernate.cache.EhCache.get(EhCache.java:113)) Element for org.jboss.portal.core.impl.model.portal.ObjectNode.children#414 is null
                      2006-02-06 01:03:41,935 WARN [org.hibernate.cache.ReadWriteCache] (org.hibernate.cache.ReadWriteCache.handleLockExpiry(ReadWriteCache.java:214)) An item was expired by the cache while it was locked (increase your cache timeout): org.jboss.portal.core.impl.model.portal.ObjectNode.children#414
                      


                      • 8. Re: portal management response time > 3 secs !
                        Viet Master

                        normally the first time you access it should load a bunch of nodes from the db and then they should be cached for later use making the page load faster.

                        • 9. Re: portal management response time > 3 secs !
                          pmn92 Novice

                          What I did was very simple : change my log4j.xml to some unsane value. My mistake! thanks.