Revision 54466998437ee65e92c55966e936151d76d4ba11 authored by ARUNACHALAM THIRUPATHI on 24 August 2014, 19:58:38 UTC, committed by Arunachalam Thirupathi on 15 September 2014, 20:16:13 UTC
Client either writes/reads from socket, never does them together. So the buffer can be shared which will bring down the memory requirement for the client by half. But the client has to watch for 2 things 1) On Write the buffer expands as necessary. So the buffer needs to be reinitialized if it grows. 2) On Read, if the buffer can't accomodate it grows as necessary, this case also needs to be handled. This works as expected and the unit tests are passing. Will put it through VPL to measure the efficiency of the fixes.
1 parent b8dbbe7
File | Mode | Size |
---|---|---|
eclipse_templates | ||
fun_projects.txt | -rw-r--r-- | 3.6 KB |
hash_ring.graffle | -rw-r--r-- | 30.7 KB |
hash_ring.png | -rw-r--r-- | 25.4 KB |
logical_arch.graffle | -rw-r--r-- | 140.3 KB |
logical_arch.png | -rw-r--r-- | 136.2 KB |
physical_arch.graffle | -rw-r--r-- | 54.0 KB |
physical_arch.png | -rw-r--r-- | 86.8 KB |
purpose.txt | -rw-r--r-- | 6.3 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...