Saving several dozen values ​​in the database in short periods of time. Is it worth it?

Question

Android

The essence of the program is as follows:
Getting geolocation data in the onLocationChanged() method every few seconds (maximum 5). Each run needs to store data for 10 to 30 fields in the database. Will it be a normal solution in terms of performance and autonomy to update the values ​​​​in the database?

Answer 1

First, it's worth worrying about thousands of records per second. Secondly, it is better not to update, but to add data. This reduces the chance of blocking, and the amount of garbage in MVCC databases, and allows you to have a history of movements.

Answer 2

Solve a business problem, if after the profile it says that it’s narrow here, optimize.