Hello all,
this is a sequence of threads in which I'm sharing some problems those I detected in B4A v10... As I have many apps developed in V 9.30 , I could compare and here it's another problem that I found.
Running huge sql asynchronous batches in my app I could notice a big difference in performance when in debug mode. See: follows a sample of log:
The SAME code that runs in 41 seconds in debug mode spends only 1 second after compiled (the sql insert batch) - I mean, the code inserts asynchronously 446 records in 1 second after compiled, but lasts 41 seconds in debug (!!!) . This is very bad because when programming sometimes we need to run the same code piece many times and spend 41 seconds for each isn't reasonable when you know that the device has resources to run in 1 second.
This is also a signal that something is going wrong in debugger...
Please, does anybody is having similar problems?
this is a sequence of threads in which I'm sharing some problems those I detected in B4A v10... As I have many apps developed in V 9.30 , I could compare and here it's another problem that I found.
Running huge sql asynchronous batches in my app I could notice a big difference in performance when in debug mode. See: follows a sample of log:
B4X:
Debug Mode:
returned 446 lojas - start insert at -> 18:01:44 -> here the code started to add a sql batch job
Started running query batch at 18:02:25 -> here the code finished the insert job - 41 seconds (!!!)
Insert result true at 18:02:27 -> exec batch - only 2 seconds!
START populate list at 18:02:27 registros -> 446
FINISH populate list at 18:02:28 registros -> 446
Compiled (with logger bridge active):
returned 446 lojas - start insert at -> 18:04:12 -> same job
Started running query batch at 18:04:13 -> 1 second (!)
sending message to waiting queue (sleep)
Insert result true at 18:04:15 -> 2 seconds
START populate list at 18:04:15 registros -> 446
FINISH populate list at 18:04:16 registros -> 446
The SAME code that runs in 41 seconds in debug mode spends only 1 second after compiled (the sql insert batch) - I mean, the code inserts asynchronously 446 records in 1 second after compiled, but lasts 41 seconds in debug (!!!) . This is very bad because when programming sometimes we need to run the same code piece many times and spend 41 seconds for each isn't reasonable when you know that the device has resources to run in 1 second.
This is also a signal that something is going wrong in debugger...
Please, does anybody is having similar problems?