javiermaestro

Heh. If only they mandate to replace a majority of the crappy wooden + single-pane windows they have in most houses, that let all of the heat out and wind and noise in, with normal, double-glaze windows with good insulation, they would cut the energy footprint in HALF, I'm sure...

LOL I re-read the article and found the specs. I really read it but somehow managed to skip the paragraph or something :-?

Anyway, my point stands. I'd use a single instance in which the dataset fits in memory, just for completeness. Then, you can compare one mongo with the full dataset to one stampede.

As you said, the aggregated data will still make Mongo suffer, but it will be a better comparison. I still like the 3-shard setup, though. It's also a good reference point.

Hi there!

Stampede looks nice, congrats!

Quick question about the 100x performance claim and the benchmarks in https://www.8kdata.com/blog/announcing-torodb-stampede-1-0-b...:

- I don't see any specs and/or methodology published for any of the benchmarks. I'd like to see some specs for the servers used (especially RAM and what HDD or storage type was used).

- For the 500GB dataset, I assume that it didn't fit in memory, but the 100GB could be "easily" fit in memory. I'd like to see if that's the case, and how does it compare when the dataset is all in memory (I'm anticipating that Mongodb still sucks big time, but it's nice to see a clear apples to apples comparison).

Anyway, kudos for the awesome work!

Yeah, exactly like in Spain, where all these things are done in the Civil Registry (Registro Civil). I mean, the article is like a huge WTF... somebody needs to travel / read about other countries, etc...

Minor nit: I think your comment would be greatly enhanced if you changed some stereotypes, e.g. "soccer-mom" for "soccer-parent", "senile old" for "old" or "people with less reflexes" and "boy-racer" for just "racer". None of those relate 100% to the gender or age of the driver, IMHO :)

First of all, thanks a lot for such an awesome tool!

I think graphite would greatly improve by having the "web" part split into different apps/packages (API, graphing and frontend/dashboard).

That way, people could install whatever they wanted. Imagine "only" having to improve the backend while other people create amazing dashboards (which, right now, is already happening anyway... there's such a fragmentation in the available frontends...)

I'd love to help with the split if you deem it worthy & if you need a hand :) I will create a GH issue anyway :D

Again, THANKS!

Cool! The final piece of the puzzle for easy and quick OAuth integration!!

Thanks! :)