Optimise Trace Generation (Except Hub)
Closed this issue · 2 comments
DavePearce commented
The Trace.java
file produced by corset
for all of the modules is very inefficient places. Some examples:
- Every
i8
requires2
bytes per element (i.e.16
bits) - Every
i32
requires8
bytes per element (i.e.64
bits) - Every
i64
requires32
bytes per element (i.e.256
bits)
For more details, see Corset issue#160.
At this stage, we don't have to do all the modules in one go. In particular, I will not update the hub with this issue, but will leave that for future.
DavePearce commented
So, for the 531
trace files generated from running the tests in this repository. Originally, they produced 6.7G
of data; now with all modules except hub
updated, they produce 5.1G
of data. Its definitely an improvement, though I was hoping for more :). I guess the hub
is a big part of the reason here.
letypequividelespoubelles commented
I(ve updtated the HUB trace in #748