Is the version of MongoDB significant now?

[cmoore]

I started down this road because I'm seeing some very unusual behavior with cursors, timeouts, and nils being passed to under any sort of load.

Here is the output of "(cl-mongo-test:quick-test)". This is running on mongo v. 2.0.6

https://gist.github.com/3344618 - Specifically "finding documents with a selector"

[fons]

Looking at the output in the gist, I see two issues : one is with the javascript interpreter ; the other with the index test.
The javascript piece relies on parenscript which may have changed which could account for the fails. The indexing relies on there not being any other index set up at the time of the test which on occasion may not be the case. That said, as far as the indexing is concerned maybe mongodb did change. I haven't been keeping up on this so that maybe possible..

[cmoore]

Ok, I'll continue digging into it and see what I can find out.

[cmoore]

Just in case you or someone else might see something I'm missing, here is the data I have so far.

mongodb 1.7.6 test output: https://gist.github.com/3349901
server log file during the test: https://gist.github.com/3349948

1.8.5 test: https://gist.github.com/3349915
server log: https://gist.github.com/3349959

2.2.0 beta: https://gist.github.com/3349920
server log: https://gist.github.com/3349964

[fons]

I tested mongodb version 2.0.7 (which seems to be the latest stable version). The results are here : https://gist.github.com/3382590. I can't reproduce your results, esp the javascript issues. On the other hand my test isn't completely clean either, but I don't see any real show stoppers..

[fons]

What's your lsip environment ?

[cmoore]

sbcl 1.0.58 on osx 10.8

From your gist...

---- starting test of package : { finding documents  } ---------------
INDEX failed: 
Expected 0 but saw 36
   DESCRIPTION => "assuming first document has index 0"
FIRST-INDEX failed: 
Expected 21 but saw 26
   DESCRIPTION => "testing assumption of first index value"

That seems like an error to me - is that the javascript part you are referring to or something else?

I'll bring up a vm and see if I get these errors on freebsd or linux.

[fons]

Agreed.
I'm taking a closer look at this. I want these tests to be clean..

On Aug 17, 2012, at 5:43 PM, Clint Moore wrote:

sbcl 1.0.58

From your gist...

---- starting test of package : { finding documents } ---------------
INDEX failed:
Expected 0 but saw 36
DESCRIPTION => "assuming first document has index 0"
FIRST-INDEX failed:
Expected 21 but saw 26
DESCRIPTION => "testing assumption of first index value"
That seems like an error to me - is that the javascript part you are referring to or something else?

I'll bring up a vm and see if I get these errors on freebsd or linux.

—
Reply to this email directly or view it on GitHub.

[cmoore]

Have you successfully used this in a multithreaded setup? I only see this when there's more than a couple of handlers trying to talk to mongo at the same time.