Re:How adding indexes to our MongoDB really improved our per...
by zoobert on Thursday November 15, 2012 @09:40AM
(#4788691)
I totally agree with you. What is the lesson here ?
You need indexes to speed up queries in any structured data storage. Uh, great but I am worried about the glipho backend then. All this to get a bit of advertising.
Re:How adding indexes to our MongoDB really improved our per...
by jamestoyer on Thursday November 15, 2012 @08:46AM
(#4788468)
I think the point here is that many people don't realise indexes matter so much in MongoDB. Their documentation doesn't go out the way to push indexes as a must. That coupled with the ease at which you can just start using it compared to say, MySQL, means that people find it interesting.
I will point out that while I wrote this, it was more to try and ensure other people don't make the same mistakes.
Re:How adding indexes to our MongoDB really improved our per...
by diziet on Thursday November 15, 2012 @07:46AM
(#4788275)
I might be nitpicking, but your blog's permanent and space taking headers make the user experience very unwelcoming, and make the whole site feel unwieldy -- slow scrolling and a good amount of space being taken over for no reason.
Re:How adding indexes to our MongoDB really improved our per...
by wodlander on Thursday November 15, 2012 @08:10AM
(#4788341)
Hi, thanks for the feedback! It's not my blog actually, we are a startup (hence the top bar for users), we will take the feedback on board, maybe we got a little excited with the size of the topbar :)
Re:How adding indexes to our MongoDB really improved our per...
by phlyingpenguin on Thursday November 15, 2012 @11:32AM
(#4789304)
Worse than that: from my end on Chrome (beta) running in Ubuntu, the bars appear to stay in their original location when scrolling which makes them cover content and generally bug out. I could not read the article at all!
Re:How adding indexes to our MongoDB really improved our per...
by fbeeper on Thursday November 15, 2012 @08:46AM
(#4788465)
Hi there!
I've been a Glipho user since its recent launch... and I'd definitely say that you are being nitpicking :P
This is a newborn platform. Even though, it has a lot of things to do, it is a nice approach. You can't expect it to be a perfect fit in every way yet, can you?
Nevertheless, this post was about MongoDB, why focusing on usability?
Re:How adding indexes to our MongoDB really improved our per...
by jaredstenquist on Thursday November 15, 2012 @09:41AM
(#4788696)
Article could be made useful by showing a benchmark of indexes vs no-indexes, and showing the readers how the indexes were created. At least then we can say it's educational and has substance. Otherwise I agree this is substance-less. It's common sense that any database is slow if used incorrectly.
Re:How adding indexes to our MongoDB really improved our per...
by dkhenry on Thursday November 15, 2012 @09:24AM
(#4788629)
I am convinced that in any production database cluster If you are given the option you should disable table scans. MongoDB gives you that option, you should use it.
I don't see how one would not find this obvious after reading the mongo docs which explicitly say
> Indexes enhance query performance, often dramatically ...
I will point out that while I wrote this, it was more to try and ensure other people don't make the same mistakes.
I've been a Glipho user since its recent launch... and I'd definitely say that you are being nitpicking :P
This is a newborn platform. Even though, it has a lot of things to do, it is a nice approach. You can't expect it to be a perfect fit in every way yet, can you?
Nevertheless, this post was about MongoDB, why focusing on usability?