aweisberg

12 ms·

1.
by aweisberg 13y ago
I have the same grandfathered plan. I wish I had bought more storage when it was available. It looks like we aren't getting any upgrades not that I blame them.
2.
by aweisberg 13y ago
I would be really surprised to find that a tree is faster then a fast cryptographic hash function like SIP hash. Cache misses to main memory are worth 10s of instructions and that number is going up in many cases. Hash functions can be pret
3.
by aweisberg 13y ago
This is actually an important topic for me. I am implementing a sharding distribution based on consistent hashing using MurmurHash3 as hash function. I am taking the first 4-bytes of the hash function output and using that. I checked and Mu
4.
by aweisberg 13y ago
A secret seed is not sufficient to prevent DoS vulnerabilities. That is one of the things the creators of SIP hash demonstrated. You can create collisions with MurmurHash3 that work regardless of the seed.
5.
by aweisberg 13y ago
For the last 18 years or so I have been taking some form of low cost Ritalin with a co-pay between 15-25 dollars. This ancient medication that is a generic costs 130 dollars a month and that is the negotiated rate! The money isn't goin
6.
by aweisberg 13y ago
Is comparing a hex-core to a quad-core apples to apples? Haswell per core performance is still better although it will be a long time before we see a hex-core part.
7.
by aweisberg 14y ago
The intent of the test was to measure throughput. Since the API is asynchronous that means the client was submitting as much work as would fit in the queues at both client and server and any latency measurement would be a measurement of how
8.
by aweisberg 16y ago
Neoview and Teradata are OLAP databases. OLTP is a different problem.
9.
by aweisberg 16y ago
NoSQL doesn't mean NoDurability. Many of them offer better multi-datacenter durability and availability by dropping ACID for BASE. I suspect that most data by volume belongs in a BASE database. Some of them also support a mixture of immedia
10.
by aweisberg 16y ago
kbd+ is a column store (analytic database) and does not partition horizontally. The two things they have in common is that they are both in memory (and kdb+ not necessarily) and support SQL as a query language (kdb+ only supports SQL like s
11.
by aweisberg 16y ago
Redis does not support partitioning so it is even more apples to oranges then VoltDB vs. Cassandra. Both VoltDB and Cassandra rely on adding nodes to scale.
12.
by aweisberg 16y ago
VoltDB replicates synchronously.
13.
by aweisberg 16y ago
MongoDB partitioning support is still under development. Probably more apple to oranges then VoltDB vs. Cassandra.
14.
by aweisberg 16y ago
http://wiki.apache.org/cassandra/Durability "Cassandra's example configuration shows CommitLogSync set to periodic, meaning that we sync the commitlog every CommitLogSyncPeriodInMS ms, so you can potentially lose up to that much data in a
15.
by aweisberg 16y ago
"Cassandra writes to disk. VoltDB is an in-memory database. So I gave both systems plenty of RAM to hold the data set and turned Cassandra's consistency settings pretty low." So in memory in both cases. Cassandra has to write a log, but not