Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
The Problem
Here is an actual problem. Why do we need to optimize the placement of data in actual memory rather than the database connectivity process?
The plan starts off with the direct interaction of every record with the database (in simple words, we get one record at a time in memory, and send it instantly to the database). With the help of this approach, we don't need to worry about the memory space we have on the client side or server side. It depends on whether the process is taking place on the client machine or sever machine (if both of the processes are running on different machines), or in case both (client and server processes) are using the same memory resources as running on the same machine. Then, the total memory space available to both of them will be considered because we hope that the size of one record would not exceed the available memory limitation in any case.
Is there any problem with this approach? Of course there is! If we opt for this approach, we don't need to go into the discussion of how to use memory efficiently. But in this case, this is the least-efficient solution because every time you contact your database to store one record, you have all the overheads to establish the connection and have definite time lags because of I/O rounding and network congestion.
Finally, after analyzing the problem, we know that to really optimize the overall performance of the application, we have to use the available memory as efficiently as possible because it's the only way to get the fastest reaction and overall performance (and it doesn't matter whether we are talking about the client or server side).