BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.staging.osgeo.org//foss4g-2022//talk//JKV73V
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-foss4g-2022-JKV73V@talks.staging.osgeo.org
DTSTART;TZID=CET:20220826T093000
DTEND;TZID=CET:20220826T100000
DESCRIPTION:Due to its SQL-based engine\, the OpenSource Software pgRouting
  is the most flexible routing engine available.\nA common misconception is
  that pgRouting is the least performant routing engine.\n\nSo how to keep 
 both performance and flexibility with pgRouting ?\n\nMany factors should b
 e taken into account.\nTo begin with\, the use cases.\nWhat level of preci
 sion do you need ?\nWill you be computing short or long routes ?\nWill the
 re be many routes computed at the same time ?\n\nSimplification is the mos
 t common way to deal with performance issues.\nHowever\, when accuracy is 
 at the core of decision making\, a minimum level of precision must be kept
 .\nReducing the number of rows the routing engine will have to process is 
 the number one tip to enhance performances.\nBut there are many other tech
 nical and functional optimizations that can make pgRouting run much faster
 .\n\nWe will look at some choices we had to make in various projects.\nHow
  the data is the first key to optimization.\nBut also how to help the rout
 ing engine make the best of it.\nWhich algorithms are best used for which 
 use cases\, and how fine tuning the database can help too.
DTSTAMP:20260404T100350Z
LOCATION:Room Verde
SUMMARY:pgRouting optimization: from technical to functional - Laure-Hélè
 ne Bruneton
URL:https://talks.staging.osgeo.org/foss4g-2022/talk/JKV73V/
END:VEVENT
END:VCALENDAR