I might be implementing this somehow in this days. Seems a good feature to have. Thanks for the report, I'll let you know any news.

@friedPotat0 @nickforddesign I made a pull request #8 can you help me test if that works to fix this issue? you can checkout the branch and test it locally using the example app

@jperelli
I'd love to test this out with a vue app using a lot of markers, but I can't get the bulk_test branch to build. build successful with yarn

I'm getting this error - not exactly sure why though :(

[Vue warn]: Error in beforeDestroy hook: "TypeError: Cannot read property 'removeLayer' of undefined"

setVisible: function setVisible(newVal, oldVal) {
      if (newVal == oldVal) return;
      if (this.mapObject) {
        if (newVal) {
          this.mapObject.addTo(this.parent);
        } else {
          this.parent.removeLayer(this.mapObject);
        }
      }
  }

@jperelli Thanks for trying to implement the feature.

I was able to build the example successfully with Poi.
After deployment the example took about 1 minute to completely show all the markers on the map. The site was not responding at all during this period. I also tested the chunk options mentioned in Leaflet.markercluster doc but it seems like the page is just locked until all markers are added successfully to the map. I logged the values in the chunkProgress-function to see the progress but there is only one output in the console at the very start of the adding progress. Most times I receive a "Paused before potential out-of-memory crash" from the Chrome dev tools and the page doesn't load up at all.

The original markercluster doc has two examples for bulk adding with chunk progress: One with 10,000 and one with 50,000 markers to add (https://github.com/Leaflet/Leaflet.markercluster#user-content-handling-lots-of-markers). The 50,000 marker example only takes about 5 seconds to load all markers!

ok, thanks for the reports, evidently the proposed solution is not working. I'm thinking if this is a problem with the implementation I made or if this is a problem with vue's v-for performance. Can't find any help on fixing vue's v-for performance easily, so I'll check my code and let you know if I can improve it somehow.

Any comments on the pull request are infinitely welcomed :)

The _add function in the Vue2LeafletMarkercluster component is called twice. Once in the mounted function and a few seconds later in the watcher for the options prop again. That is the reason why I got only one output of the chunkProgress-function. The second _add destroyed or stacked with the first adding progress in any way. After commenting out the options watcher I get a page load with the progress logged in every interval when setting the clusterOptions to:

clusterOptions: { chunkedLoading: true, chunkInterval: 200, chunkDelay: 50, chunkProgress: function (processed, total, time) { console.log(processed, total, time) } }

But the overall page loading time is still very bad in comparison to the example.

Okay, figured out that there is a setTimeout function in the example component which causes the options prop to be rewritten after 5 seconds. If you remove these lines the bulk adding only gets called once when mounting the markercluster. Probably the function is there for testing purposes only?!

Right, the setTimeout was for testing purposes. I will make two test files, one only for bulk. I'll modify the PR today in a couple of hour. Thank you for your help!

No problem. Please keep in mind that the build command of vue-cli is no longer useable for building your examples. When using vue build somefile.vue, like it's written in your package.json for building, it throws an error saying:

We are slimming down vue-cli to optimize the initial installation by removing the vue build command.
Check out Poi (https://github.com/egoist/poi) which offers the same functionality!

I fixed this by installing Poi npm i poi -D and adding a new index.js to the main script in the package.json.
Content of the index.js:
`import Vue from "vue";
import Example from "./example";

new Vue({
el: "#app",
render: h => h(Example)
});`

After that I could build the example by running npx poi build.

Hope this helps not only for the bulk testing but for the normal example, too.

Alternatively the process could also be done with yarn like @skinnyjames mentioned earlier but I didn't test it.

I modified the examples, but couldn't improve performance.
Maybe vue or vue2leaflet are adding some overhead.

Please let me know if the new Pull Request is ok or if you see that it runs slow
run with:

yarn example_bulk

I got marker clusters to work well with vue as a standalone library. If it helps, I can take a closer look soonish!

Yes please :)

Hi all,
I looked into it, and I redesigned a bit how vue2leaflet components are initialized
(using an event bus instead of deferredMountedTo)
It might not be the best way, but components like marker cluster, are working a lot faster with lots of markers.
There is a provisional working demo at https://github.com/skinnyjames/mapa

git clone https://github.com/skinnyjames/mapa
npm install
cd examples && poi app.js

Would love to hear thoughts.