Handling memory allocation with pgrouting in centrality analysis

Hi @cvvergara and @rnanclares,

Thank you so much for your quick response!

I can try the pgr_betweennessCentrality to compare the results. We are using the edge betwenness centrality, but instead of considering all possible pairs of nodes in the network, we created a set of origin and destination. In any case, the new function seems totally relevant for the analysis! thank you very much. I will see how I can use it (I still have a lot to learn)

Then, It sounds to me that it will be an important new feature. That’s great, looking forward for the 3.6.3 release.

Sharing the data using a database dump sounds now to me as the best option. I was not aware. Please, find here the link with the data. There are two files:

  • A database dump of the tables involved: osgeo_pgrouting_dump.sql
  • A query script that execute the different sizes on that database performance_quries.sql

Very well observed. It is indeed a limitation. Probably there is a way to add some distance to the boundingbox (line 252) depending on the scale. For example + 0.01º .

I tried two options:

  • Option A: Local machine with a total memory of 15G
  • Option B: Server machine with a total memory of 47G

Again, thank you very much for your prompt and kind responses. Please, if there is a problem with any query or the database dump, let me know.

1 Like