Re: request for feature
- Posted by useless_ Sep 25, 2012
- 1228 views
Suggestion: Perhaps it would be better to stop thinking in terms of threads/tasks and start thinking in terms of processes. Have a separate program for each procedure you want to execute. When the procedure completes, the program ends and the memory is automatically freed. A separate program/process can also take advantage of multi-core CPUs better than threads can (most OS implementations tend to keep all threads for a given process on the same core). Communication between processes can be handled via sockets or files (producer / consumer model).
That's always been a fine idea, but the startup time hurts too much, we are talking 4 seconds on my slow 2.4Ghz machines, Cojabo reported startup times of 2 sec when running news.ex. I tried to get around this with prestarting on a different computer, but then i had to know in advance what i was going to do, and the oem quit making parts for my time machine.
The other alternative we cannot do is string execution, else i'd have one procedure to take a filename and load the file as a string and run it.
I still keep coming back to task ID exhaustion, and memory clogging up.
useless
