|
Apr
26 |
|
awarded | Custodian |
|
Apr
26 |
|
reviewed | No Action Needed gprof not showing call graph |
|
Apr
9 |
|
asked | How to memory map (mmap) a linux block device (e.g. /dev/sdb) in Java? |
|
Apr
4 |
|
awarded | Yearling |
|
Apr
4 |
|
comment |
Kyoto Cabinet HashDB inserts are not O(1) msiz, as I mentioned is 2 GB. I changed bnum to 1 Billion, and its still the same. |
|
Apr
4 |
|
comment |
Kyoto Cabinet HashDB inserts are not O(1) The system's total RAM usage is just around 1.8 GB, out of which the KC process is using about 1.2 GB. So I am assuming that the index is not being kept in the RAM. Is it true? How can I force it to keep the index in the RAM? |
|
Apr
4 |
|
comment |
Kyoto Cabinet HashDB inserts are not O(1) Does KC keep the keys in the memory? Or does it fetch them from the disk for every write? I don't see any documentation mentioning that for HashDB, though they do mention it for B+ tree. |
|
Apr
4 |
|
asked | Kyoto Cabinet HashDB inserts are not O(1) |
|
Apr
3 |
|
asked | Kyoto Cabinet HashDB Max "free block pool power" (MAXFPOW) is 20? |
|
Mar
27 |
|
accepted | Couchbase Java getAndLock confusion |
|
Mar
27 |
|
comment |
Couchbase Java getAndLock confusion I'm using the official client library: couchbase.com/develop/java/current |
|
Mar
27 |
|
revised |
Couchbase Java getAndLock confusion added 11 characters in body |
|
Mar
27 |
|
asked | Couchbase Java getAndLock confusion |
|
Mar
20 |
|
comment |
Key Value storage without a file system? You don't have to mount a disk in order to write to it. Are you familiar with Linux? Any new device added to the system shows up as a block device under /dev. You can read/write to it directly without mounting.
|
|
Mar
20 |
|
comment |
Key Value storage without a file system? Again, a disk has to have a file system to be mounted, yes, BUT it doesn't need to have one to be written or read to! You don't need to mount a disk to read/write to it. You only need to mount if you need to write files to its file system. |
|
Mar
20 |
|
comment |
Key Value storage without a file system? Block devices appear as a file, yes, but that does not mean that the block devices have a filesystem. |
|
Mar
20 |
|
comment |
Key Value storage without a file system? I will have to contradict you here. You are wrong here. Try this on a Linux machine. Add a new drive (lets assume its /dev/sdb). Assume there is a file test.txt with contents hello world in your home directory. Give the following commands: dd if=~/test.txt of=/dev/sdb bs=11 count=1 dd if=/dev/sdb of=output.txt bs=11 count=1. These commands will write the file to the raw drive, and then read it back into another file output.txt. If you read the output file, its contents will be hello world. Please note this will destroy the filesystem of the drive, if there was any.
|
|
Mar
20 |
|
comment |
Key Value storage without a file system? A block device does not need to have a file system, in order to read or write to it. |
|
Mar
20 |
|
comment |
Key Value storage without a file system? Replication is Mongo is "copy all of the data on another node". We are looking for something like "divide the data into 8 chunks, calculate two parity chunks, and store each chunk on 10 nodes". Tahoe LAFS uses this approach. |
|
Mar
20 |
|
comment |
Key Value storage without a file system? Sure you can access a drive or a raid array as a "block device" in Linux and read/write to it directly. |
