How CUBRID handle an expensive query on a huge table?
Hi,
How CUBRID handle an expensive query on a huge table or a recursive query?
Will CUBRID partition the big task into some smaller ones and then forward the small task to each processor (I assume the query run on multi processor server) and then merge back?
CUBRID is optimized for web services. This means that it is designed to handle small transactions under high load (lots of connections). Because of this, each query execution is single threaded and will be executed across a single core. Expensive queries will be executed as a single task which allows for better concurrency.