05-09-2023, 09:18 AM
Hi
Indeed, connections are not pooled. If you feel the need for that , please do pool them, I don't see a reason to advise you against. Just keep all the active children as children of the _CurvyGlobal_ object. But as what I always advise with perfs optimizations, prefer keeping the code simple (no connection pooling in this case) until you profil and find that connections creation/destruction is really a problem. Often what we think will be a main reason for performance decrease is not really the issue.
Indeed, connections are not pooled. If you feel the need for that , please do pool them, I don't see a reason to advise you against. Just keep all the active children as children of the _CurvyGlobal_ object. But as what I always advise with perfs optimizations, prefer keeping the code simple (no connection pooling in this case) until you profil and find that connections creation/destruction is really a problem. Often what we think will be a main reason for performance decrease is not really the issue.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.