BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pyconde-pydata-2026//talk//UUHYUS
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-pyconde-pydata-2026-UUHYUS@pretalx.com
DTSTART;TZID=CET:20260414T151000
DTEND;TZID=CET:20260414T154000
DESCRIPTION:AsyncIO vs threads isn't about "which is faster" - it's about s
 cheduling\, memory\, and the kind of load you run. We'll unpack what threa
 ds and asyncio do under the hood (OS scheduler vs event loop + epoll)\, ru
 n practical benchmarks\, and show why many "async" libraries still rely on
  thread pools (aiofiles\, Motor\, Django bridges). Then we'll repeat the s
 ame tests on Python 3.14's free-threaded (no-GIL) build and discuss when a
 n interpreter upgrade can beat an async rewrite.
DTSTAMP:20260523T180036Z
LOCATION:Platinum [2nd Floor]
SUMMARY:AsyncIO vs Threads: who survives in the No-GIL Era? - Igor Anokhin
URL:https://pretalx.com/pyconde-pydata-2026/talk/UUHYUS/
END:VEVENT
END:VCALENDAR