Kudakwashe Paradzayi

Posted on Oct 8, 2019 • Edited on Oct 9, 2019

How large is the dev.to production database 🤔

#discuss #hacktoberfest #watercooler

This month of October as we do the hacktoberfest I personally adopted the dev.to project.

Browsing though the codebase, I'm loving the way the code looks so organised and simple and the people and bots 😅 who were involved in the code certainly make it seam easy, which is very encouraging.

Now I have this burning curiosity nagging me in the back of my mind

How large is the dev.to production database? 100GB? 500GB? 2TB 😲?

Let's try guessing the size and let @ben and the @devteam tell us the answer in the end.

My guess is ≃ 250GB

Cheers 🥂
@kudapara

Oldest comments (21)

Ben Halpern • Oct 8 '19 • Edited

My guess is ≃ 250GB

This is the closest guess yet (being the first guess), but it is not correct.

Edgar Cruz • Oct 8 '19

Maybe 225GB?

Autumn • Oct 8 '19

75gb?

Dan D • Oct 8 '19 • Edited

~275GB

Stef Pletinck • Oct 8 '19

I'd guess more like 100GiB

Ben Halpern • Oct 10 '19

Winner

Stef Pletinck • Oct 11 '19

Hurray, I've won some fame!

Tushar Borole • Oct 8 '19

if you don't include an image, I guess 50GB

Angel Campos • Oct 8 '19

261GB

Casey Brooks • Oct 8 '19

I believe all uploaded images/videos are stored on a CDN, so I will not include them in my estimate. But let's get a few other numbers to try and get a better estimate.

This article has an ID of 186129, so I'll round to 200k articles for easy math.
The text in an article doesn't take up much space at all. I would guess most articles are a few KB in size, and the largest ones less than 100KB. Let's go with a median estimate of 50KB per article.
The most popular articles have a couple hundred comments, but most are probably around 10 or so. - Comments are much smaller than articles, so lets go with an estimate of 1KB per comment.
The homepage for logged-out visitors has "239,226 humans who code". So let's around to 250k registered accounts. I couldn't even begin to put an accurate estimate on the size of each account record, so lets just say 10kb to account for a bio, linked URLs, etc.

So let's do the math!

(200,000 articles * 50kb) + ((200,000 articles * 10 comments) * 1kb) + (250,000 users * 10kb) = 14.5 GB

I'm gonna put my official guess at 25 GB. Text-based media takes up much less space than you might expect!

Paweł Kowalski • Oct 8 '19 • Edited

Yeah, i would guess something around that too.

In math i would also include that this is an rails app, so basically it means it has a lot of trash in db and if using gems like papertrail, its even worse - thats why i would land at around 25GB, because i would say it should not exceed 10GB.

Abhinav Kulshreshtha • Oct 9 '19

That's very sound maths. You sir have my respect. I had a but more conservative estimation based on a blogging company I once contracted for. My estimation was 72GB rounded.

Swarup Kumar Mahapatra • Oct 9 '19

Wondering if these guys use event sourcing?? If it is , then the event store would be HUGE!. The table size would increased rapidly. The events that would be having large payload would be PostUpdated, CommentUpdated.

However i cannot estimate the numbers.