Fcalva/cyclone
1
0
Fork 0
mirror of https://github.com/justinethier/cyclone.git synced 2025-05-24 12:35:05 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Cleanup

Browse source
This commit is contained in:
Justin Ethier 2016-02-11 22:35:09 -05:00
parent 5df934dfdf
commit 0cdc09706a
1 changed files with 1 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
gc-notes.txt
View file

@ -13,20 +13,12 @@ TODO:
- read.sld in-port-table - obvious thread safety issue here - read.sld in-port-table - obvious thread safety issue here
what is the performance impact of adding locks to all these funcs? what is the performance impact of adding locks to all these funcs?
or do we need to rewrite the code somehow? or do we need to rewrite the code somehow?
- start making core stuff thread safe. for example, test.scm sometimes - start making core stuff thread safe
crashes, I think printing out result from (read)
- assume I/O and eval both have threading issues - assume I/O and eval both have threading issues
- eval.sld - ... - eval.sld - ...
- In conjunction with above, write more programs that use multiple threads - In conjunction with above, write more programs that use multiple threads
- try a simple one with 3-6 threads just writing data to output, and then files
- simple multithreaded example such as producer/consumer - simple multithreaded example such as producer/consumer
- find at least one more algorithm that can be parallelized - find at least one more algorithm that can be parallelized
- document at a high level how the GC works
mostly what minor/major GC's are, and how they are interleaved.
- user manual
need to document everything, including:
- what to be cognizant of when writing threading code. esp, how to deal with stack objects (initiating minor GC's, etc)
this probably should be part of the user manual itself
- revisit features list, issues list, etc - revisit features list, issues list, etc
DONE: DONE: