Skip to main content
MapReduce

MapReduce

Computer programWikipedia

Search complete. 34 mentions across 14 episodes found for "MapReduce".

Oct 19, 2026

speaker_0HOST
14:08
Okay.
speaker_1HOST
14:09
If you write a traditional MapReduce style script to process 100 files through a three-step process, audit, verify, report, the script will typically wait for all 100 files to finish the audit phase.
speaker_0HOST
14:21
Like an artificial barrier.
speaker_1HOST
14:22
Exactly.
Stephen IbarakiHOST
58:30
fellows, Sanjay and Jeff, and they both left, right? And in fact, they even saved Google in the year 2000, right, when Google's search engine had a problem.
Stephen IbarakiHOST
58:43
And every major kind of technical achievement, including MapReduce, They left.
Yan SolihinGUEST
58:53
Yeah.
Stephen IbarakiHOST
58:55
So, you know, we can say in the interim, we have these sort of goals we want from an education standpoint.

Unknown podcast

Anthropic's Claude Traces NIST Curve Seeds to a 1997 Unix Clock

Oct 17 · 1 Mention

speaker_1HOST
14:57
Instead of drawing your sub-agent topology by hand, A lead agent plans the task and spins sub-agents up and down in phases, with fan-out and fan-in.
speaker_1HOST
15:06
The talk says Claude Code uses a JavaScript engine for MapReduce-style jobs.
Lenar KessHOST
15:11
They open with history.
Lenar KessHOST
15:12
Ken Thompson built Unix in a month.
Sam NewmanGUEST
11:10
And so literally, it-- when a computer g- fails, the software doesn't really care.
Sam NewmanGUEST
11:15
I mean, this is way back in the days of MapReduce, right? You'd slide a tray out.
Sam NewmanGUEST
11:18
You'd find, okay, that's the hard drive.
Sam NewmanGUEST
11:20
You'd unzip the Velcro, throw it in a bin, put another hard drive in, tape on the Velcro, put it in.
John PlattGUEST
2:30
It could be a very data-heavy problem because people at Google are very, very good at large data processing.
John PlattGUEST
2:37
I mean, dating back to MapReduce and all of the large-scale computing that we have.
John PlattGUEST
2:42
And now we have lots of TPUs and AI.
John PlattGUEST
2:45
So if there's problems that we think are... scientific problems where AI can do very, very well, then we try to attack those.
Chris GambillGUEST
60:06
Well, now we have AI.
Chris GambillGUEST
60:09
So it makes those things all of a sudden possible and kind of in the window of opportunity again, which increases that mountain of work, right? That's what big data did, right? That's what Hadoop and MapReduce did, right? It increased the mountain of work.
Chris GambillGUEST
60:23
It never decreased the mountain of work.
Chris GambillGUEST
60:26
That's what cloud compute did.
Brooke HopkinsGUEST
15:16
So I like to kind of take a similar task and break it down into like paralyzed.
Brooke HopkinsGUEST
15:20
It's like MapReduce, but for humans, it's like break it down into a bunch of parallel workflows that you're like still working on the same thing, but it's doing different pieces.
Brooke HopkinsGUEST
15:29
And so you're kind of like checking in on different pieces of it.
Amir BormandHOST
15:32
Absolutely.
speaker_4HOST
3:24
If you look back, we used to rely on these incredibly clunky JVM-based Hadoop tools to do the heavy data lifting.
speaker_3HOST
3:30
And Hadoop relied on MapReduce.
speaker_4HOST
3:32
Exactly.
speaker_3HOST
3:32
Yeah.
David CrawshawGUEST
19:28
I, I wanted to do something with lots of computers or very large computers because all of my work had been basically solo open source stuff, which meant my universe was constrained to the PC or the Mac or some machine on that scale.
David CrawshawGUEST
19:43
And, uh, I had recently been doing a data analysis project with my now father-in-law, who's a professor at Haas, and, you know, I'd, I'd built this thing because the data set didn't fit in one machine, and so we found 10 machines somewhere at the university, and I, I tried to build something across them and, you know, hacked up some very crude MapReduce-looking thing-
Matt KleinHOST
20:01
Yeah
David CrawshawGUEST
20:02
... based on what I'd read about MapReduce.
Michael SlaterGUEST
8:00
Right.
Michael SlaterGUEST
8:01
And then we had Spark and MapReduce was the technical term of that day.
Michael SlaterGUEST
8:06
That was the AI of that day.
David O'HaraHOST
8:08
Yeah.

4 more episodes mention MapReduce.

Create an account to see the whole feed, search across every transcript, and follow the entities you care about.

We value your privacy

We use cookies to understand how you use our platform and to improve your experience. Click “Accept All” to consent, or “Decline non-essential” to opt out of non-essential cookies. Read our Privacy Policy.