If the disk is performing normally and the query is similar that were used earlier for benchmarking, I do not see any solid reason. However, can you check if you missed to rebuild / create an index on column (say x) and the update query says where x=....

check the execution plan to confirm it is not scanning the table, an if it is probably you have missed one index.