[
https://issues.apache.org/jira/browse/IGNITE-16912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-16912:
-----------------------------------
Epic Link: IGNITE-16923
> Revisit UUID generation for RowId
> ---------------------------------
>
> Key: IGNITE-16912
> URL: https://issues.apache.org/jira/browse/IGNITE-16912
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> Current implementation uses UUID.randomUUID, which comes with a set of
> problems:
> * some people say that you can't avoid collisions this way. Technically it's
> true, although I don't think that it's a real problem
> * secure random is slow when you use it frequently. This can affect
> insertion performance
> * random uuids are randomly distributed, this can be a problem for RocksDB,
> for example - if most insertions will go to the tail, this can improve
> overall write performance
> There are interesting approaches in this particular document, we should take
> a look at it:
> https://datatracker.ietf.org/doc/draft-peabody-dispatch-new-uuid-format/
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
