Google Appengine Intro for Stockholm Django Usergroup

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Lite om appengine. 2 delar, först lite översikt och lite siffror för att ge er en idé om vad appengine är bra på. Sen skriver vi en _liten_ app och deployar den på appspot.






    Hur många känner till appengine?


    Hur många har skrivit kod för appengine?













    Inte för att visa hur väl appengine skalar eller så utan mer för att ni lite enklare ska kunna komma igång





    1 Favorite

    Google Appengine Intro for Stockholm Django Usergroup - Presentation Transcript

    1. Google AppEngine - Web apps in teh cloud
    2. [jag är inte så duktig på python & django]
    3. Python Molnet Skalbart Ruby Java(!) Django Gratis* Distribuerat Enkelt* BigTable Inlåst Ovant Ungt Begränsat
    4. Webbappar? • Webapp (CGI, WSGI) • Google Accounts • PIL • urllib • Mail • Cron jobb • Memcached • Datastore • Non-relational • GQL • Det svåraste (enligt mig)
    5. Numbers everyone should know - enligt Brett Slatkin • Writes are expensive! • Datastore is transactional: writes require disk access • Disk access means disk seeks • Rule of thumb: 10ms for a disk seek • Simple math: 1s / 10ms = 100 seeks/sec maximum • Depends on: • The size and shape of your data • Doing work in batches (batch puts and gets) 
    6. Numbers everyone should know - enligt Brett Slatkin • Reads are cheap! • Reads do not need to be transactional, just consistent • Data is read from disk once, then it's easily cached • All subsequent reads come straight from memory • Rule of thumb: 250usec for 1MB of data from memory • Simple math: 1s / 250usec = 4GB/sec maximum • For a 1MB entity, that's 4000 fetches/sec 
    7. The Lessons - enligt Brett Slatkin • Writes are 40 times more expensive than reads. • Global shared data is expensive. This is a fundamental limitation of distributed systems. The lock contention in shared heavily written objects kills performance as transactions become serialized and slow. • Architect for scaling writes. • Optimize for low write contention. • Optimize wide. Make writes as parallel as you can. 
    8. Kod
    9. Frågor?
    10. http://delicious.com/hinkeb/appengine Följ mig på twitter @henrikberggren

    + Henrik BerggrenHenrik Berggren, 7 months ago

    custom

    622 views, 1 favs, 0 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 622
      • 622 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 8
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories