 Stan Gurtler
|
b8662cc18f
measure memory usage during runtime automatically
|
%!s(int64=3) %!d(string=hai) anos |
 tristangurtler
|
f5d5621937
at large scales, synchronization was breaking down. This fixes that
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
635aeb1e48
fixing some instrumentation stuff
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
9254fdd76b
added instrumentation
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
33e41b4eb5
Cleaning up code to be more legible, and checking it with valgrind
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
3980749a6c
various bugfixes, and further establishing the environment for testing
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
3cce4c56e4
server/client now compile, at least
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
3e75082ddb
updates to networking code
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
4715de0aad
networking code upload; it doesn't compile yet, and there's a small delta left on the client code before that's ready anyways. But the server code has been drafted; needs to be debugged
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
da32b7a842
minor changes that lead to ~30% reduction in proof time
|
%!s(int64=3) %!d(string=hai) anos |
|
tristangurtler
|
373a1adbae
I don't know what it is, but approximately 3% of the time, there is a bug that causes proofs to fail. Otherwise, I'm adding networking code now
|
%!s(int64=3) %!d(string=hai) anos |
