Forum: Other

Post: PerfGuide doc Corrections and Suggestions

PerfGuide doc Corrections and Suggestions
pmartel
Feb 29, 2012
p.2 2.1 Use of the term "replication" here as a synonym for K-safety may contribute to later confusion when "replicated" is used as a distinction from "partitioned" tables.

p.6 2.4.1 "between when it sends back the results, your application handles the results, initiates a new procedure call, and the call reaches the VoltDB server" -> "while it sends back the results, your application handles the results and initiates a new procedure call, and the call is transmitted to the VoltDB server"

p.22 4.3 "Instead, manages unused memory..." -> "Instead, VoltDB manages unused memory..."

p.22 4.3 "Simialrly, the Java runtime and the operating system perform similar memory pooling techniques." -> "Similarly, the Java runtime and the operating system perform their own memory pooling."

p.23 4.4 "where the application code controls exactly how" -> "where the VoltDB system implementation code controls exactly how" avoids confusion with the "(user) application (specific)" code (Java stored procedures).

p.24 4.5 "be very careful before setting a low maximum heap size." -> "be very careful when setting a low maximum heap size."

p.26 5.1 "(a 1/10th of a second)" -> "(1/10th of a second)"

p.26 5.1 "Which is why keeping time skew" -> "This is why keeping time skew" making a complete sentence.

p.26 5.2 'VoltDB doesn't care whether the cluster view of time is "correct" from a global perspective, but it does care..." -> "it doesn't matter to VoltDB whether the nodes' view of time is "correct" from a global perspective. What does matter is'

p.29 5.2.4 "it can use itself be a reference server." -> "it can use itself as a reference server."