2 ms·
Because an operation may be a query for a single document by an indexed field, or it could be an FTS across billions of records, each with thousands of terms.
by vrtx0 10y ago
Because an operation may be a query for a single document by an indexed field, or it could be an FTS across billions of records, each with thousands of terms.
In my experience, MongoDB and MySQL performance are usually on par. It's important to understand what the operations are before making any kind of comparison.
That said, I totally understand why this was your first thought. The article doesn't even state if the operations are queries, updates or inserts, let alone how many indexes or scans are performed...
- spimmy 10y agoThe article was written by people who don't understand very basic things about databases. To be fair, this is part of Mongo's pitch: come use a database, you don't need DBAs or people who know things about databases. Which is always gonna be kind of a lie. So they invite this on themselves.\ I hate when I get reduced to sounding like a mongo apologist, but it's their own fault for not following any best practices with data.
- deleted 10y ago[deleted]