2012/2/12 Lars Helge Øverland larshe...@gmail.com:
Hi,
I think the important thing here is to improve the user feedback
mechanism, not the extra thread itself. First, in my opinion it is
easier to provide user feedback this way - the current arrangement is
to start a separate thread and then
Depends really on the use case for import-export. There should really
be very few cases where routine import/export should ever take close
to 30 seconds. I recall the 300 000 data values we imported from the
dummy ihris data in Kenya took around 8 seconds. Even so, I think the
30 second
2012/2/14 Jason Pickering jason.p.picker...@gmail.com:
Depends really on the use case for import-export. There should really
be very few cases where routine import/export should ever take close
to 30 seconds. I recall the 300 000 data values we imported from the
dummy ihris data in Kenya
Hi,
I think the important thing here is to improve the user feedback
mechanism, not the extra thread itself. First, in my opinion it is
easier to provide user feedback this way - the current arrangement is
to start a separate thread and then request/ping that thread
continuously and
Hi Jason
Thanks for the detailed response. I'm trying to look right now at
incremental improvement of the current process by providing better
feedback to users - running a single thread instead of the background
cave process can provide a quick win here.
More generally, I would like to move
One of the difficulties of providing good user feedback on import is
the that we spawn an extra thread to do the actual importing and we
don't have very sophisticated inter-thread communication with that
worker beyond the status message which is a transient thing. And
better logging is not a
Hi Bob,
As usual I have an opinion.
First and foremost, the import process as I think everyone knows, is rather
fragile. I am glad to see a few of the issues being fixed (thrown, uncaught
exceptions!). In distributed systems, we do not have full control over the
metadata of course as has been
7 matches
Mail list logo