veyepar: Limiting Execution Time Through Interrupt Driven Programming

Author(s):	Erik van Zijst
Location	Tasman B
Date	jul Sat 06	Days Raw Files
Start	15:10	First Raw Start	14:53
Duration	0:30:00	Offset	0:16:46
End	15:40	Last Raw End	16:16
Chapters	00:00 0:21:37
Total cuts_time	27 min.

http://2013.pycon-au.org/schedule/30061/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host archive public mp4 svg png

assets release.pdf Limiting_Execution_Time_Through_Interrupt_Driven_Programming.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

This talk explores the challenges of ensuring responsiveness of applications under varying conditions like suddenly increased load, code regressions and problematic user data that reveal code paths with unusually high time complexity.

I'll be looking at interrupt-driven techniques to help bring the 95 percentile of the response times of your application closer to the (usually much lower) mean.

In this talk, we'll go beyond traditional tricks like caching, sharding and data denormalization and instead look at tools that can interrupt execution of overly expensive code paths, such that you can guarantee an upper bound in response time.

Interruptingcow and django-timelimit will be some of the tools that will be covered in this talk.

The context for most of this is web applications, and I'll be drawing many examples from our ongoing experiences with running and scaling Bitbucket, which is entirely written in Python.

Having said that though, many of the tools and techniques demonstrates will apply just as well to other types of applications and situations.

Comment:

production notes