work summary

I tried to run the rulecache simulation on the baleen machine to get the timing with the actual traffic traces. I was unable to do so because the program would seg fault and crash.

I did discover that in the newer version of the files on baleen already calculate the average time to update the rule cache and print this value out with the other statistics.

I found some filetraces of the program that were on baleen. I took a look at the filetrace_5dims-0updatetime.out trace file. This runs the simulation with the RHL size varrying between 16 and 23. I graphed the average time to update the rule cache as the simulation was running and here are the results:As you can see the average update time starts out high and then goes down to a couple milliseconds as the simulation runs. The last average update time was 8.99 milliseconds.

I took a look at some of the other filetraces on baleen, some of them start with RHL size of 1, this had a significantly higher update time, around 2-3 seconds.

If I can't get the program to run I will next take a look at the correlation between the RHL size and the time to update the cache in the other traces.