All of that is going to ENTIRELY depend on your hardware, and how fast it's going to allow the electrical pulses and actual processing of the different chips on your mobo, and the kind of data you're going to be adding, requesting, and removing. There's no clear-cut answer with the information provided.
You're going to get throttled if this sits in a VM, bar none. If you have other machines that are running on the host, you've got a few layers in the stack between your VM and the metal that needs to handle your data, as well as other data in the other VMs. Mind you, if you have a VM sitting solo on your host, you'll be darn near 1:1 for Metal:VM speeds, but it isn't exactly 1:1. You're going to get throttled if you have other processes taking disk IO and CPU. You're going to get throttled at your database design if you don't include indexes. You're going to get throttled at the volume of data you're adding and deleting (It'll be faster to delete as SQLite just marks space as being available and overwrites existing data, but then you could be looking at fragmentation not only in the database, but, the disk as well) The type of file system you're using can also be a throttle point. The physical database size doesn't really come into play, unless you're talking billions of index records that needs to be dealt with per call. Actual data is returned to your application one row at a time, not as a full chunk of data for your entire request. On any query, SQLite will reference indexes heavily (If available, and if it makes sense), and doesn't touch/look@ anything it doesn't need. The more hardware you throw at it, the faster you're going to get, but on top of that, ultimately, you're limited by the speed to which the electricity flows through the tiny little wires and connections. On Fri, May 3, 2019 at 10:02 AM Zhu, Liang [AUTOSOL/ASSY/US] < [email protected]> wrote: > Hi Sqlite experts, > > In my current project, we have the need to inserting and deleting data to > and from the database between 1 and 10 ms for 24/7. I am seeking the > clarification on the following questions > > > 1. what is the throughput requirements are possible using Sqlite API?, > in other words, what is the max speed can my inserting and deleting > operation be? > 2. When we inserting and deleting data at the speed mentioned above, > what kind database maintenance do we need to do to maintain the performance > of the database? > 3. How is constant deleting and insert effect the database performance? > > > Thank you, > > Liang Zhu | Lead Software Engineer | Branson Ultrasonics > Emerson Automation Solutions | 41 Eagle Road | Danbury, CT 06810 | USA > T (203) 796-2235 | F (203) 796-0380 > [email protected]<mailto:[email protected]> > > The information contained in this message is confidential or protected by > law. If you are not the intended recipient, please contact the sender and > delete this message. Any unauthorized copying of this message or > unauthorized distribution of the information contained herein is prohibited. > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
