View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000017 | Timekoin Server | Performance Issue | public | 2012-06-23 22:45 | 2012-08-03 16:24 |
| Reporter | KnightMB | Assigned To | KnightMB | ||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.2 | ||||
| Target Version | 1.3 | Fixed in Version | 1.5 | ||
| Summary | 0000017: New Timekoin servers take too long to update transaction history | ||||
| Description | A fresh timekoin server is suppose to start at record 4 (after the beginning record and the 3 test records for verification) and work it's way towards the end using the other peers as a way to build up the transaction history. Instead, the new timekoin server might jump right to the end and begin building the transaction history from the front instead (working backwards), which takes a lot more time. | ||||
| Steps To Reproduce | Start a new timekoin server where the transaction history is empty. | ||||
| Tags | No tags attached. | ||||
|
|
I was able to reproduce after a few tries on a test server, seems to be a situation where the server is about to start building the transaction history but instead gets a notification from a peer that record number (some high number) is invalid and redirects it to repair it. The repair request is valid because the blank database won't have a record that far in it, but that redirects Timekoin to start working on the database near the end of the records instead of starting from the beginning and building up. |
|
|
If you schedule a block check at say 3 for example, this will restart the process because it will start at the beginning of the transaction history and begin working it's way back up like before. It can still get interrupted by a peer request for invalid block check, so some further code will be needed to make it a little smarter. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-06-23 22:45 | KnightMB | New Issue | |
| 2012-06-23 22:45 | KnightMB | Status | new => assigned |
| 2012-06-23 22:45 | KnightMB | Assigned To | => KnightMB |
| 2012-06-23 22:47 | KnightMB | Note Added: 0000012 | |
| 2012-06-23 22:47 | KnightMB | Status | assigned => confirmed |
| 2012-06-24 17:02 | KnightMB | Note Added: 0000016 | |
| 2012-06-24 17:02 | KnightMB | Note Edited: 0000016 | |
| 2012-08-03 16:24 | KnightMB | Status | confirmed => resolved |
| 2012-08-03 16:24 | KnightMB | Fixed in Version | 2.41 => 1.5 |
| 2012-08-03 16:24 | KnightMB | Resolution | open => fixed |
