Hi there! I'm a developer from semilimes. We're trying to use Tryton as a cloud ERP. So, unchaining trytond from some particular DB on launch was our first problem, which was solved thanks to Cedric's advices during the TUB'16 (thank you a lot for that, greatly appreciated!!)
Now we have another blocker on the road - the Pool building process is too long to be fired on every request. And we cant afford collecting Pools for all of the DBs in memory, since it will eat all the available memory pretty quick. So we have an idea: rewrite a small part of the pool.py module, so that it will build only the currently needed classes for the particular request, i.e. patch the "Pool.get()" method mostly. And throw the data away after request. So, we hope that building only a small part of all the classes out there will cut the building time a lot, and will allow us to do so on each request without significant response time lags. There is a difficulty with building only a specific class, not all at once, since right now Pool just loops through all of them. We think of building some sort of "maps" for each class, that will allow us to quickly understand, what exactly and how to build for each needed class. So, the question is - what do you guys think about it? Are we just plain crazy, or this is a possible way to go? Or maybe you know some simplier solution for this problem, do you? Really, just interested in your opinion, guys. Thank you! -- You received this message because you are subscribed to the Google Groups "tryton-dev" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton-dev/05972e03-dfba-46b7-a220-025ea3813395%40googlegroups.com.
