[jedc]

They've reported receiving 1million applications per year. If even a fraction of those get interviewed (with 1-5 interviews per candidate) that's a good chunk of data. Correlate that with regular performance reviews of 30k employees... I'd say that's a small Big Data problem.

[raverbashing]

30k? Data. Not Big Data

And "Small Big Data" is probably data as well.

[ownagefool]

He's not talking about 30k rows, he's talking about 30k people. It could easily be big data if you monitor & document their every working moment, but they probably aren't doing that so you're probably right.

[raverbashing]

Yes, 30k people, so it's what? Some interview reports, some performance reviews, HR report/history of the employee?

It really doesn't look like something big.

[jedc]

1 million applications received. Say 10% of those go into some sort of evaluation process = 100k assessments/year. Say 10% of those go through an interview panel of (on average 3 interviews) = 30k assessments/year For 30k employees with (say on average) 2 assessments per year = 60k assessments/year.

So 1 million CVs per year on which to do some sort of evaluations, and 200k individual assessments per year. Over the past five years that roughly 6 million data points.

Since there's no hard-and-fast rule on this, that's why I called it small Big Data.

[chris_mahan]

Even if it's 100 million rows. That's something a single beefy server with SQL Server 2012 can handle. That's not big data.

Big data is a million times 100 million rows.

[shawabawa3]

> Big data is a million times 100 million rows.

[citation needed]

This whole thread is pointless. There is no definition of Big data.