When should you think about database sharding?

i've been thinking about database performance lately, our app is growing, and we've kind of hit a wall with just one big database. read replicas help with reads, sure, but they don't do anything for write bottlenecks. so, i'm wondering when other people have had to start thinking about database sharding. what specific problems or numbers really told you it was time to get into that more complicated setup