[SERVER-10386] Mongo queries via MongoMapper become incredibly slow on OSX 10.8 Created: 31/Jul/13 Updated: 10/Dec/14 Resolved: 02/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tyler Merritt | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | OS X |
| Participants: |
| Description |
|
Forgive that I don't know the right project where I should log this issue. Please review this SO post for history: http://stackoverflow.com/questions/17904881/mongo-mapper-rails-queries-suddenly-taking-100-ms Right now mongo queries have double again: MONGODB (265.7ms) creative_development['jobtypes'].find({:merchant_id=>"518b762e89651a0389000013"}) I've tried repairDatabase, clean, drop the database and restore data, uninstall mongo, reinstall, new version of mongomapper (gem 'mongo_mapper', '>= 0.13.0.beta1'), I am well and truly out of ideas here. Please give me some idea why it went from 0.2 ~ 0.5 ms response time locally to over 250ms now... |
| Comments |
| Comment by Tyler Merritt [ 02/Aug/13 ] |
|
Gents I ashamedly request we cancel this ticket - error was tracked down to Couldn't see the forest for the trees. Tyler |