https://issues.apache.org/bugzilla/show_bug.cgi?id=54960
--- Comment #9 from Jan <[email protected]> --- 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? 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. Look, I don't really care what you guys do with mongometer, I've donated it, I'm not looking for any credit and I'm not looking to support anything; you guys asked for it, so I gave it to you. The last thing I'd add on this is, you'd be better off keeping the free text area/scratch pad area, sticking to a single sampler and creating a script-to-java layer. You don't open a separate mongo shell for each type of query, so why should you have to with jmeter? The script to java mapping layer not only allows you to adhere to the DRY principle, it also allows for better unit test coverage, and reduces the number of separate samplers that have to be written and maintained. My 2p. -- You are receiving this mail because: You are the assignee for the bug.
