monzero-core.git/src/blockchain_db/blockchain_db.h, branch v0.10.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.02016-08-31T09:03:32Zcore: faster find_blockchain_supplement2016-08-31T09:03:32Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-30T15:39:33Zurn:sha1:6cf8ca2a7f3e11ca5559018dfc9b20869c07cdce
Since this queries block heights for blocks that may or may not
exist, queries for non existing blocks would throw an exception,
and that would slow down the loop a lot. 7 seconds to go through
a 30 hash list.
Fix this by adding an optional return block height to block_exists
and using this instead. Actual errors will still throw an
exception.
This also cuts down on log exception spam.
move the rct commitments to the output_amounts database2016-08-28T20:29:02Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-29T18:55:49Zurn:sha1:59a66e209a844ac6d4221f7c04141b32fa2823c3
Since these are needed at the same time as the output pubkeys,
this is a whole lot faster, and takes less space. Only outputs
of 0 amount store the commitment. When reading other outputs,
a fake commitment is regenerated on the fly. This avoids having
to rewrite the database to add space for fake commitments for
existing outputs.
This code relies on two things:
- LMDB must support fixed size records per key, rather than
per database (ie, all records on key 0 are the same size, all
records for non 0 keys are same size, but records from key 0
and non 0 keys do have different sizes).
- the commitment must be directly after the rest of the data
in outkey and output_data_t.
blockchain_db: add functions for adding/removing/getting rct commitments2016-08-28T20:28:11Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-04T13:18:37Zurn:sha1:eb56d0f9941d4aed9d89a20007221cecd1dc6cbcnew unlocked parameter to output_histogram2016-08-01T21:16:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-01T21:16:00Zurn:sha1:1593553e03aef8d44621aaf79a33ba25f69a2bd7
This constrains the number of instances of any amount
to the unlocked ones (as defined by the default unlock time
setting: outputs with non default unlock time are not
considered, so may be counted as unlocked even if they are
not actually unlocked).
remove hf_starting_height db2016-07-13T20:38:34Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-13T20:19:05Zurn:sha1:d7b681cd6518834ce9b76676980561cb8e235cff
It's not really needed, it used to be an optimization for when
that code was not using the db and needed to recalculate things
fast on startup.
Another take on migration2016-04-24T16:46:50ZHoward Chuhyc@symas.com2016-04-10T16:25:13Zurn:sha1:2b0fa05f0d0d3c2aae90225d786d9ba7fcd6a2ff
Delete old indices and recreate them, rather than updating them
Maybe not quite as slow as before.
Merge branch 'performance' into master2016-04-05T20:13:16ZHoward Chuhyc@symas.com2016-04-05T20:13:16Zurn:sha1:d7ea7d9a23cd71bbba4d6e2822f54257432b3f01Cleanup2016-04-05T20:05:24ZHoward Chuhyc@symas.com2016-04-04T16:28:31Zurn:sha1:372acee72303b4d7ea225981c523d328fda297be
drop obsolete remove_output()
fix get_output_key(global), fix crash in blockchain_dump
Cleanup and clarify2016-04-05T19:57:45ZHoward Chuhyc@symas.com2016-04-04T01:10:58Zurn:sha1:591e421875988ea63313a7da22062f62f06b30ab
Try to rationalize the variable names, document usage.
Schema update: tx_indices - consolidate the tx subdbs from 5 to 32016-04-05T19:54:06Zwarptangentwarptangent@tutanota.com2016-03-04T19:56:36Zurn:sha1:9aadedb1d0eb4f922b33edfa0ede1f4d1ac128d1