special table (UINT_UINT) 500million rows takes up 3.9GB
2 views
Skip to first unread message
Jak Sprats
Jan 25, 2011, 11:14:53 PM1/25/11
to redisql-dev
Hi All,
Another optimisation is what I call the UINT_UINT table, it is when a
table consists of 2 UINTS (one PK UINT and one column UINT).
this table has been optimised for speed and performance
Inserting 500million rows takes up 3.9GB, takes 100minutes, and runs
at 82K/s.
Putting an index on the 2nd column (given 1000 different values) adds
1.8GB and takes 5.5 minutes to build.
The phenomenal memory usage is by storing both of the UINTs INSIDE the
Btree, this is a very optimal data structure.
This can be used for a variety of things and at this speed and memory
usage, you can put so many rows in
- Jak
Another optimisation is what I call the UINT_UINT table, it is when a
table consists of 2 UINTS (one PK UINT and one column UINT).
this table has been optimised for speed and performance
Inserting 500million rows takes up 3.9GB, takes 100minutes, and runs
at 82K/s.
Putting an index on the 2nd column (given 1000 different values) adds
1.8GB and takes 5.5 minutes to build.
The phenomenal memory usage is by storing both of the UINTs INSIDE the
Btree, this is a very optimal data structure.
This can be used for a variety of things and at this speed and memory
usage, you can put so many rows in
- Jak
Reply all
Reply to author
Forward
0 new messages