mongodb in deep

IN DEEP@flaper87

domingo 2 de octubre de 11

MEMORY MAPPED FILES

WHERE ISdomingo 2 de octubre de 11

IT EATS AS MUCHAS IT CAN FIND

MEMORY MAPPED FILES



LRU’d VIRTUAL MEMORY

MEMORY MAPPED FILES



LRU’d VIRTUAL MEMORY

SO THAT’S WHEREYOUR MEMORY IS


SO THAT’S WHEREYOUR MEMORY IS

WHAT ABOUTTHE LOCK?


READERS-WRITER LOCK


IF LOCKED THEN EQUE

READERS-WRITER LOCK


PER-COLLECTION LOCK

IF LOCKED THEN EQUE

READERS-WRITER LOCK


CANNOT BE CHANGED

SO, IT USESA B-TREE!


CAN BE INTERPRETED

CANNOT BE CHANGED



ONE INDEX AT A TIME

CAN BE INTERPRETED

CANNOT BE CHANGED



YES, IT USESA B-TREE!

WHAT ABOUTTHE CPU?domingo 2 de octubre de 11

ONE INDEX AT A TIME

YES, IT USESA B-TREE!

WHAT ABOUTTHE CPU?

If you’re telling itsomething, it’ll use one


A B-TREE!WHAT ABOUT

THE CPU?If you’re telling it

something, it’ll use oneIf you’re asking it

something, it’ll use onedomingo 2 de octubre de 11

WHAT ABOUTTHE CPU?

If you’re telling itsomething, it’ll use one

If you’re asking itsomething, it’ll use *

If there’s JS in there,it’ll keep using one


WHAT ABOUTTHE CPU?

If you’re asking itsomething, it’ll use one


MULTITHREADEDMAP/REDUCE?


WHAT ABOUTTHE CPU?


MULTITHREADEDMAP/REDUCE?


NOT POSSIBLE(until V8 is finalized)



LOCKS INVOLVED:



LOCKS INVOLVED:READ



LOCKS INVOLVED:READ MAP



LOCKS INVOLVED:READ MAP + EMIT




REDUCEdomingo 2 de octubre de 11



REDUCE WRITEdomingo 2 de octubre de 11

ONE INDEX AT A TIME

Sm, v8 or ?!?!

Scripting Interface

v8 is the way to godomingo 2 de octubre de 11

v8 is the way to go

ONE INDEX AT A TIME

Sm, v8 or ?!?!

Could it be Java?


ONE INDEX AT A TIME

It could also be Python

Could it be Java?

Sm, v8 or ?!?!


It could also be Python

ONE INDEX AT A TIME

Sm, v8 or ?!?!


!anks, 10gen!

Reach me on twitter: @flaper87domingo 2 de octubre de 11

mongodb in deep

Technology