Also, for the benefit of everybody following this thread: Please note that the performance is very much optimized for the most frequent operations primarily involving READs, and such optimizations have introduced minor side effects to performance of infrequent operations such as WRITEs. This is by design. While we continue to find ways to improve these scenarios, there might be situations like the process of tenant creation which involves multiple registry-WRITEs becomes considerably slow.
One way of solving such issues is to reduce the number of WRITEs or evenly spread out the calls such that the waiting time for the user is reduced. However, from a QA-team's PoV, we should not consider these issues to be blockers but as major usability improvements that can be taken into consideration if time permits. Thanks, Senaka. On Thu, Aug 8, 2013 at 11:46 AM, Senaka Fernando <[email protected]> wrote: > Hi Evanthika, > > Having a mount and not having a mount (at least based on recent > performance tests) did not show significant differences in times. However, > if the mounted DB is either remote (or local and heavily loaded) a delay of > a certain factor is expected. I don't think that it should be considered to > be show-stopper. > > Thanks, > Senaka. > > > On Wed, Aug 7, 2013 at 5:26 PM, Evanthika Amarasiri <[email protected]>wrote: > >> Hi, >> >> We tried several combinations of configurations to figure out the cause >> for the delay we noticed in tenant creation. At the end, we found out that >> the cause is the registry mount. *Without* a registry mount, it took ~8 >> seconds for the tenant creation. *With* a registry mount, it took ~60 >> seconds. >> >> When there were no registry mounts but when the primary user store was >> connected to an Oracle DB, it took ~30 seconds to create the tenant. >> >> Regards, >> Evanthika >> >> >> >> On Fri, Jul 26, 2013 at 6:06 PM, Afkham Azeez <[email protected]> wrote: >> >>> I ran this with JProfiler, and the problem is due to caching with >>> Hazelcast & the registry caching handler, clearAncestry method which >>> recursively gets called. As can be seen from the attached screenshot, the >>> Hazelcast EntryIterator.hasNext is a very expensive method which involves >>> object deserialization. Senaka, can we optimize the clearAncestry method? >>> >>> >>> >>> >>> On Thu, Jul 25, 2013 at 4:53 PM, Shashika Ubhayaratne <[email protected] >>> > wrote: >>> >>>> Hi, >>>> >>>> We observed that tenant creation is very slow on cluster set up. It >>>> took more than 3 minutes. >>>> In addition to that,more than 15 minutes taken to create 4 >>>> concurrent tenants. Once logged in to tenant, it navigates to carbon UI >>>> console as per the attached screenshot. Also note that some tenants could >>>> not logged in. >>>> >>>> Refer the bug [1] for more details: >>>> [1]: https://wso2.org/jira/browse/CARBON-14225 >>>> >>>> Thanks, >>>> Shashika >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> > > > -- > * <http://us13.wso2con.com/> > * > * > * > *Senaka Fernando* > Senior Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > * > Lean . Enterprise . Middleware > -- * <http://us13.wso2con.com/> * * * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
