Cursor Timed out error on MongoDb cursor?

I have just tried this out with 100,000 simple documents $totalCount for me is always 100000, regardless of whether $count and $startIndex are set (this is the correct behaviour) $entries contains all 100000 entries. The whole operation takes about 3 seconds on my local setup Are you using a remote database? It's possible the network is what is causing the timeout rather than MongoDB What size are your documents?

The volume of data can affect the speed.

I have just tried this out with 100,000 simple documents. $totalCount for me is always 100000, regardless of whether $count and $startIndex are set (this is the correct behaviour). $entries contains all 100000 entries.

The whole operation takes about 3 seconds on my local setup. Are you using a remote database? It's possible the network is what is causing the timeout rather than MongoDB.

What size are your documents? The volume of data can affect the speed.

Danielwood Yes, I am using remote database , but it is also on local network(Intranet). Might be that problem will be because of $cursor->count(); And also $cursor->count() increases execution time. If I am not using $cursor->count() It is performing fast as you said.

– Maulik Vora Sep 7 '10 at 17:56.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.