React-leaflet: Q: Large Numbers of Markers

Created on 3 Sep 2017  路  2Comments  路  Source: PaulLeCam/react-leaflet

I'm working with this library and need to render ~50k markers. While it's functional, on Chrome it can be very slow with the standard markers/icons and popups disabled. using marker elements, are there any recommendations for improving performance?

Also is a key prop necessary for Marker components?

Most helpful comment

That's unfortunate, and tbh a tad blunt. but I would recommend the following:

  • make this clear in the new issue template, that's a full day I could have gotten an answers or feedback wasted. Don't waste your users time, e.g.:
<!-- For questions and general questions, please use the react-leaflet tag on Stack Overflow --!>`
<!-- https://stackoverflow.com/questions/tagged/react-leaflet --!>
  • add a note on the kind of performance one can expect to the readme, aka a ballpark figure of how many markers it can comfortably hold. There are things you can do and you can send people to stack overflow. It could be as simple as _"React Leaflet allows you to add hundreds of markers"_, which sets expectations without mentioning numbers

But as an aside, speaking as a Stack Exchange moderator, Stack Exchange explicitly forbids what you've just suggested to me, but since it's StackOverflow that's the exception, but that doesn't mean everything is appropriate there:

https://stackoverflow.com/help/product-support

  • How do I? -- Stack Overflow (tell them what tags to use -- your product and language at minimum)
  • I got this error, why? -- Stack Overflow
  • I got this error and I'm sure it's a bug -- file an issue (on your own site)
  • I have an idea/request -- file an issue (on your own site)
  • Why do you? -- your own community (developer forum etc)
  • When will you? -- your own community

So feature requests, questions about your plans for the library, questions about why you built it a certain way, would all get closed as off topic and out of scope.

All 2 comments

Hi,
Please only use GitHub issues to report possible bugs in the library.
You can use the react-leaflet tag in StackOverflow for general questions about it.

That's unfortunate, and tbh a tad blunt. but I would recommend the following:

  • make this clear in the new issue template, that's a full day I could have gotten an answers or feedback wasted. Don't waste your users time, e.g.:
<!-- For questions and general questions, please use the react-leaflet tag on Stack Overflow --!>`
<!-- https://stackoverflow.com/questions/tagged/react-leaflet --!>
  • add a note on the kind of performance one can expect to the readme, aka a ballpark figure of how many markers it can comfortably hold. There are things you can do and you can send people to stack overflow. It could be as simple as _"React Leaflet allows you to add hundreds of markers"_, which sets expectations without mentioning numbers

But as an aside, speaking as a Stack Exchange moderator, Stack Exchange explicitly forbids what you've just suggested to me, but since it's StackOverflow that's the exception, but that doesn't mean everything is appropriate there:

https://stackoverflow.com/help/product-support

  • How do I? -- Stack Overflow (tell them what tags to use -- your product and language at minimum)
  • I got this error, why? -- Stack Overflow
  • I got this error and I'm sure it's a bug -- file an issue (on your own site)
  • I have an idea/request -- file an issue (on your own site)
  • Why do you? -- your own community (developer forum etc)
  • When will you? -- your own community

So feature requests, questions about your plans for the library, questions about why you built it a certain way, would all get closed as off topic and out of scope.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

josdejong picture josdejong  路  4Comments

benzen picture benzen  路  4Comments

gane5h picture gane5h  路  3Comments

kaitlynbrown picture kaitlynbrown  路  3Comments

rolfdalhaug picture rolfdalhaug  路  3Comments