With this the default thread will use 10 MByte for response buffers, 2 MByte for request buffers and 2 MByte for the
JSON request. There is also a bit of memory used for other data structures used in NDB API and in response handling.
These are normally of smaller size.
A RDRS server can serve a very high request bandwidth with 16 threads. A normal set up of an RDRS server would
use about 2 threads per CPU available. The RDRS server would scale to about 10 CPUs for one cluster connection
and a bit more with multiple cluster connections. It is possible to scale with many RDRS Servers and each will be able
to handle millions of key lookups.
With this the default thread will use 10 MByte for response buffers, 2 MByte for request buffers and 2 MByte for the JSON request. There is also a bit of memory used for other data structures used in NDB API and in response handling. These are normally of smaller size.
A RDRS server can serve a very high request bandwidth with 16 threads. A normal set up of an RDRS server would use about 2 threads per CPU available. The RDRS server would scale to about 10 CPUs for one cluster connection and a bit more with multiple cluster connections. It is possible to scale with many RDRS Servers and each will be able to handle millions of key lookups.