You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using AceBase as a database with Node-Red in a docker configuration. I setup the configuration with AceBase Server (rather than embedded) with the idea that, due to the single-threaded nature of the Node.js event loop, that running AceBase in a separate process would provide better scalability, and even allow me to deploy AceBase Server onto a separate virtual machine.
However, I have seen benchmarks from other database servers that can run in a separate process/server vs. embedded that embedded can be much, much faster.
Anybody made any observations or tests, or even just a gut-feeling on whether using AceBase embedded rather than AceBase-Server may or may not be a better choice?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using AceBase as a database with Node-Red in a docker configuration. I setup the configuration with AceBase Server (rather than embedded) with the idea that, due to the single-threaded nature of the Node.js event loop, that running AceBase in a separate process would provide better scalability, and even allow me to deploy AceBase Server onto a separate virtual machine.
However, I have seen benchmarks from other database servers that can run in a separate process/server vs. embedded that embedded can be much, much faster.
Anybody made any observations or tests, or even just a gut-feeling on whether using AceBase embedded rather than AceBase-Server may or may not be a better choice?
Beta Was this translation helpful? Give feedback.
All reactions