[CSHARP-341] mongodb server memory problems Created: 16/Oct/11  Updated: 12/Nov/18  Resolved: 06/Apr/15

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: 1.3.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: liulijun Assignee: Unassigned
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows server2008 64bit



 Description   

When mongodb consumed all the memory, the write speed slower and slower.

mongodb gridfs collect a large number of files, then use five threads write large files, the beginning of the fast, when the server is mongodb memory occupied by all, the writing speed slower and slower. How do I make it, in order to avoid such a problem will it? The main work on the master server is written, it did not need a lot of memory mapping



 Comments   
Comment by Robert Stam [ 17/Oct/11 ]

The connection pool should limit the number of connections to the server to 100 per client. The server writes an entry to the log every time a connection is opened or closed, so if there is a problem with the number of connections you should see evidence of that in the server logs.

What is the total size of the files being uploaded, and what is the amount to RAM on your server? Perhaps you are just reaching the point where the working set no longer fits in memory, at which point you would see a slow down because your bottleneck then becomes disk I/O.

Comment by liulijun [ 17/Oct/11 ]

but i think the c# driver is send command to the server ,maybe the question is the connection pool ,but i test is not the question.

Comment by Robert Stam [ 16/Oct/11 ]

Do you think this is a C# driver problem, or is it really a question about the mongod server?

Generated at Wed Feb 07 21:36:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.