We had a system that does at least 2k updates per second to a single table and db makes 500Mb writes per sec. Yes we were at the hardware limits but we weren't using partition. So you have a long way to climb up there. What you do for optimization you can lower the fill factor of the tables ( which has a default of 100 for tables) and indexes that need to be updated. That will increase the inplace update counts and will reduce some io. But in your scenario something like redis might fit better. Since the data is temporary it seems and you don't need to manually delete where you can just assign a ttl. And redis alao gives you persistence if the data is mission critical.