Most technology choices are reversible with effort. Database choice is one of the few that compounds, since schema, query patterns and operational habits all grow around it.
The question worth asking early isn't which database is fastest, but which failure modes the team is prepared to operate through. A database chosen for its guarantees under partial failure tends to age better than one chosen for benchmark numbers.