Georg Leciejewski

Any update on this? btw @Sean-Der nice workaround, worth considering a single go file!

Sorry @Matthijsy , i did close a couple of issues just for cleanup and thought there has been no work on this. If you can provide any links or infos...

This can have a lot of causes since your description is not very dedicated! But still a little hint: If you are running elastic via docker you may need to...

i tested this merged version and the job times stayed the same for ~1500 jobs, instead of runtimes increasing with each job. I am creating highcharts images for ~300.000 charts...

GREAT! I ran test with a couple of thousands items and chained two other jobs after the main payload (create 5k imgages => run png_optimizer => clean upload cache folder)....

```ruby class CreateImagesWorkflow < Gush::Workflow def configure(klass_name) klass = "RI::Chart::Cmd::#{klass_name}".constantize # finds all codes and schedule single jobs ~3000-30.000 per kind cnt = 0 img_jobs = klass.codes.map do |code| run...

+1 after reading the code for an hour and trying to puzzle things together. Btw any progress on https://github.com/koding/kite/issues/39 ?

i have similar problems with big files containing 10-20000+ rows. To me it seems the whole structure is read into memory, opposed to lazy loading a sheets rows? I have...

Awesome finding! Looking foreward to it.

same problem here and the ms office 10 error message does not offer any further infos :-(