neolempires2@gmail.com wrote:

> if data inserted to table about 100 data/sec,is the script run well in
> this condition, and no data lost or error??

The best way to find out is to actually set up a test.

I've seen the following method used in production systems; it avoids
forcing the insert process to wait for an immediate response, and also
allows trying again later in case of problems.

* insert the data into an intermediate table with a column indicating
order of insertion
* separate process, launched on a schedule or by a human operator:
- note the most recent record that exists
- process all rows up to and including that one, either deleting
them or marking them as already processed
- any rows inserted mid-process are left for the next launch