On Fri, 23 Dec 2016 at 16:02 Gregory Mace <macegh...@gmail.com> wrote:
> [cut] > > Still it seems like 1/2 a second for pool creation and .820 seconds for > acquiring the first connection seems a bit much to me. > > Yes, but we don't know how much of this time is related to orient and how much is related to the system itself: lot of processes, full ram and so on. I will measure on my side Also, in light of the sizable hit for registering classes, is there a way > to move the registration of domain jar to the server itself. Perhaps in a > plugin or dropped into the lib directory? > > NOTE : I put the "software architech" hat. For sure, you can do that, even if in the mid/long term It looks very error prone: - domain is updated, nobody deploy the new jar, nothing works anymore. - domain is updated, ready to dploy the new jar, the db can't be switched off - ... So, take in consideration ALL the tradeoffs, even the impossible ones, because impossible happen. If you need to register only the very fisrt time, put a flag, or use a dedicated "register process" to do that job only one time. My 2€cents -- Best regards, Roberto Franchini OrientDB LTD - http://orientdb.com -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
