Re: [sumo-user] multithreading options

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

- option --threads is not recommended at this time as it produces only marginal speed up and only in special cases

- option --threads brings no advantage whatsoever to pedestrian simulation

- sumo option --routing-threads takes no effect for pedestrian routing (only vehicular routing)

- duarouter option --routing-threads speeds up pedestrian routing. You can use duarouter to convert your walks with from-to into walks with edges and speed this up with parallel routing. Then load the walks with edges in sumo for a faster simulation.

regards,

Jakob

Am Mo., 22. Sept. 2025 um 22:28 Uhr schrieb Joan Carmona Mercadé via sumo-user <sumo-user@xxxxxxxxxxx>:

 

Hi,

 

I have a pedestrian-only simulation, without traffic lights, composed of different sets of files with a multitude of elements like

 

<walk from=edge1_id to=edge2_id/>

 

The question is: would I get a faster simulation time using a multithreading-related option, such as --thread or --device.rerouting.threads ?

 

And also, how do I choose the right step-length value to minimize execution time without significantly affecting the results?

 

Thanks,

Joan

 

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user