# Why does sequencer bound timestamp increment?

**URL:** https://forums.foundationdb.org/t/why-does-sequencer-bound-timestamp-increment/4494
**Category:** FoundationDB Core
**Created:** [May 31, 2024, 4:56pm UTC](https://forums.foundationdb.org/t/why-does-sequencer-bound-timestamp-increment/4494 "2024-05-31T16:56:56Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![pdeva](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/pdeva/32/1655_2.png) [@pdeva](https://forums.foundationdb.org/u/pdeva)
#### Post date: [May 31, 2024, 4:56pm UTC](https://forums.foundationdb.org/t/why-does-sequencer-bound-timestamp-increment/4494/1 "2024-05-31T16:56:56Z")

</div>

its this line in `getVersionCxx`

> <https://github.com/apple/foundationdb/blob/f1d8c5fd5ad56fbacd628bdcd3927fe88e5ed5d5/fdbserver/masterserver.actor.cpp#L177>

why is the timestamp increment bounded by `MAX_READ_TRANSACTION_LIFE_VERSIONS` at all? why not just have it increment by ` VERSIONS_PER_SECOND * (t1 - self->lastVersionTime)`