is there any software engineering wisdom that can be displayed about the decision making which led to polling being chosen over event driven in the first place? Are there any watch words to the wise to be avoided here? On Monday, February 9, 2015, Norbert Hartl <norbert@hartl.name> wrote:
Am 09.02.2015 um 22:19 schrieb stepharo <stepharo@free.fr <javascript:;> :
I have an installation where a pharo powered hardware is used in a closed case. Over time that collects quite some heat. One reason for this is that the pharo vm is taking approx. 6% CPU all the time. The only thing that happens is network/sockets. I suspended the ui thread in the image but on this platform it doesn't help. Are there any tweaks to lower the polling and the activity of the image/vm even more? Right now having an event driven VM is the way but it is not on the horizon. JB was starting to look at that when he worked on the android part. Are the prerequisites for having things event driven known? Is that a huge task for the vm if things need to call in instead of being called?
I do not know. What I can tell you is that we are doing our best and I'm try to get funding. This is three years that I apply to EU funding and fail :). But if I get it I have 8 years engineers planned.
I know is hard. Thank you very much to try harder :)
We'll make it somehow ;)
Norbert