Advertisement
Guest User

Untitled

a guest
Mar 19th, 2019
119
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
C 1.20 KB | None | 0 0
  1. I noticed that each query is taking between .6 seconds to 1.5 second.
  2. I believe this is where the delay is coming from:
  3. Because if each query takes on average 1 second and you have 500,000 records
  4.  
  5. 500,000 * 1 = 500,000 seconds
  6. -> 8333 minutes
  7. -> 138 hours
  8.  
  9. DEBUG | 03/19/2019 07:05:42.788 | UPDATE `tbl_hist_results`
  10.                                                            >>  43.781 - 42.788 = 0.993 seconds
  11. DEBUG | 03/19/2019 07:05:43.781 | UPDATE `tbl_hist_results`
  12.                                                            >>  44.372 - 43.781 = 0.591 seconds
  13. DEBUG | 03/19/2019 07:05:44.372 | UPDATE `tbl_hist_results`
  14. DEBUG | 03/19/2019 07:05:44.893 | UPDATE `tbl_races`
  15.                                                            >>    46.423 - 44.893 = 1.53 seconds
  16. DEBUG | 03/19/2019 07:05:46.423 | UPDATE `tbl_hist_results`
  17. DEBUG | 03/19/2019 07:05:47.134 | UPDATE `tbl_hist_results`
  18.                                                            >>        47.13446.423 = 0.711 seconds
  19. DEBUG | 03/19/2019 07:05:47.374 | UPDATE `tbl_hist_results`
  20.  
  21.  
  22. Is it possible to get the query run at 0.1 second or something, or can we debug to find out why this part is
  23. taking so long.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement