MongoDB stress test -
i'm doing test mongodb. version of mongo 2.4.9. , in database have more 2.5 millions of documents inserted in collection like:
[{"_id": _id, "id" : _id, "row1": "0000-000000000-000000000-00", "meta" : "domainname", "type" : "domaintype", "timestamp" : "01234646458", "relations" : { "direct" [], "indirect": ["domain1", "domain2"]}, "extension" : "net", "usage" : "intranet","extravalue":math.random()}, ...] the collection indexed, , working inserting data, problem occurs when i'm trying read randomically data database, aprox. 100 threads searching non-specific document each 2 seconds (each 2 seconds new operation starts). operation simple, read document , insert new document linked (only reference) other document, operations doesn't affect randomically search. first 255 minutes, work good, after 25 minutes connections closed or refushed. cpu usage normal , network usage normal too, other database didn't have same problem. exist consideration in moment read data mongo? or maybe problem of driver? now, test node.js , mongo mongodb mongoclient driver.
i suggest checking if issues originating on server or client. on server can check following:
- mongod logs evident issues being reported
- ulimits server - assuming mongod instance running on linux (or flavor of unix) server.
on client can check for:
- if on linux / unix, check ulimits
- checks pooled connections
- does restart of client application resolves problem? if so, client issue, making server checks useful in case.
Comments
Post a Comment