# Lazy optimization takes \>100s

**URL:** <https://discuss.elastic.co/t/lazy-optimization-takes-100s/45621>\
**Category:** Kibana\
**Created:** [March 28, 2016, 6:51pm UTC](https://discuss.elastic.co/t/lazy-optimization-takes-100s/45621 "2016-03-28T18:51:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lwintergerst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lwintergerst/32/18164_2.png) [@lwintergerst](https://discuss.elastic.co/u/lwintergerst)\
**Post date:** [March 28, 2016, 6:51pm UTC](https://discuss.elastic.co/t/lazy-optimization-takes-100s/45621/1 "2016-03-28T18:51:05Z")

</div>

Hi,

I just tried to give writing kibana plugins a try.

AFter every change I have to wait \> 100s for the optimization finishes.

I'm running it on my local laptop (~2y.o, 2,7GHZ core, 16BG RAM, SSD), using Windows (the setup was time consuming and may be the problem. I might just use a linux VM...)

The plugin itself is the one Tim Roes writes in his ["Writing Kibana 4 Plugins"](https://www.timroes.de/2015/12/02/writing-kibana-4-plugins-simple-visualizations/) blog post.

Is there any way to make it faster?

---

<div class="post-metadata">

**Author:** ![stormpython](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stormpython/32/7190_2.png) [@stormpython](https://discuss.elastic.co/u/stormpython)\
**Post date:** [March 29, 2016, 4:27pm UTC](https://discuss.elastic.co/t/lazy-optimization-takes-100s/45621/2 "2016-03-29T16:27:32Z")

</div>

You can try adding a `kibana.dev.yml` file under the `/config` directory. Add this to your `kibana.dev.yml` file:

```auto
optimize:
   sourceMaps: '#cheap-source-map' # options -> http://webpack.github.io/docs/configuration.html#devtool
   unsafeCache: true
   lazyPrebuild: false

```

---

<div class="post-metadata">

**Author:** ![lwintergerst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lwintergerst/32/18164_2.png) [@lwintergerst](https://discuss.elastic.co/u/lwintergerst)\
**Post date:** [March 30, 2016, 1:10pm UTC](https://discuss.elastic.co/t/lazy-optimization-takes-100s/45621/3 "2016-03-30T13:10:19Z")

</div>

Thanks for the response.

I just tried it real quick. It seems to be working much better now. I will report back in 1-2 days to confirm it once I had time to test it thoroughly.

Luca

---

<div class="post-metadata">

**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\
**Post date:** [March 30, 2016, 4:57pm UTC](https://discuss.elastic.co/t/lazy-optimization-takes-100s/45621/4 "2016-03-30T16:57:26Z")

</div>

Yeah 100s is extraordinary (even when optimizations are not enabled). Are you seeing excessive CPU usage before optimization starts?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:57pm UTC](https://discuss.elastic.co/t/lazy-optimization-takes-100s/45621/5 "2017-07-06T13:57:24Z")

</div>