https://issues.apache.org/bugzilla/show_bug.cgi?id=54960
--- Comment #11 from Mikhail Epikhin <[email protected]> --- to Jean-Paul, >>Good luck with this approach. Apart from violating the DRY principle, this >>approach is rather messy architecturally. Are you planning on having a >>separate sampler for every API call? I just wrote this samplers for my coworkers. They want performance testing simple operations like insert and find. I not created it for apache jmeter and anything opensource project. Just for me, just for my coworkers. I understanding DRY principle, and as you, i want to create simple and good architecture. >>The original intention for mongometer was to enable a scratch pad, an area >>where you were not bound to any predifined interfaces, an area where you can >>experiment with your mongo scripts to compare their performance in a relative >>manner. What this, per sampler approach does it to limit the user to the >>defined samplers Okey, it's very good idea and MongoDB Java Driver have this eval-call, but it's very slow. And with this method you lock db on throughput ~500rps. What if you script have better performance? How you test it? to Philippe, >>Thanks for feedback, could you attach them as a patch ? >>I vote for their inclusion but waiting for other commiters opinion. It's good idea, but this samplers have a very slow functionality. I think, we can create samper with scripting text area (BeanShell/JSR223). In text area we can describe BSON-object or query for database. It would be more functionality, but something difficult for users. I can opensource it, but i agree with Jean-Paul. We need more functionality and simplify archetecture:) -- You are receiving this mail because: You are the assignee for the bug.
