2022 Sep 16 8:55 AM
Dear Community,
Do anyone knows how to solve problem with SQL Console forcing one core to 100% of utilization? And on top of that it works so slow that even editor can't keep up with my very lousy typing skills. 🙂
Here is the screenshot of SQL Console and CPU utilization while it's just sitting, and do nothing, but still making one core to sweat:
And here is the CPU utilization when I shutdown SQL Console:
I do use some dark theme, but I don't believe that could influence.
Btw, a link email of ADT team would be a good starting point. I have searched it several times, but it seams it's not easy to find it, at least for me. 🙂
Regards,
Nemanja
2022 Sep 18 9:09 AM
Maybe you could try first with harmless SQL code like SELECT * FROM T000 (instead of VBAP), it should return very few lines.
But you are saying than "even editor [is slow]". What do you mean? Is anything SAP working normally with your Eclipse installation?
To contact SAP, create a ticket at SAP Support with your S-User. https://support.sap.com.
2022 Sep 19 1:08 PM
Hi sandra.rossi ,
Editor of SQL console is slow, because whole Eclipse application is slowed down. I believe it's because CPU usage is increased. When I switch to another tab, lets say another editor with class or another SAP GUI window, it starts behaving normally.
But what I did discover is if I write in select statement like this:
select * from vbap where vbeln = '1234567890'
Then it gets slowed down.
But if I name the fields in SELECT clause like this:
select vbeln, posnr, erdat from vbap where vbeln = '1234567890'
Then it behaves normal. Eclipse/SQL Console is not slowed down.
Still I have to test this couple of more times to be sure in my assertion. 🙂
BR,
Nemanja
2022 Sep 30 11:58 AM
2022 Oct 03 12:16 PM
Hi bmayhs ,
If you want to have pear to pear session, please contact me. Will be glad to help. 🙂
Regards,
Nemanja
2022 Oct 03 2:06 PM
Also, you could test if you indicate all VBAP columns explicitly, does it slow down too? (I guess it should be the same "speed" as with select *)
2022 Oct 06 11:59 AM
Hi bmayhs ,
I have tested as sandra.rossi suggested with all 333 fields explicitly stated from VBAP (yes, we appended the table with ~70 columns), and result are the same. It blocks entire SQL Console. And one CPU core is at 100% all the time. Looks like "Data Preview" is the problem. Because server processing time is in milliseconds.
Hope this test helps.
BR
Nemanja
2022 Oct 06 1:11 PM
Also one thing I forgot to mention, is that when I close "Data Preview" window CPU core utilization is back to normal. Everything points to "Data Preview" window.
Data Preview is mature for serious refactoring, anyway. 🙂 Simple actions like copy cell or copy entire row are still challenging. 🙂 bmayhs ask managers to give your team time for improvements. 🙂
BR,
Nemanja
2023 Jan 05 4:37 AM
Hi Nemanja,
Thanks for the information. We will look into issue and get back to you.
We are investing in changes for Data Preview & SQL Console. You will see some of them in the upcoming releases. Looking forward for your support and feedback once you get a chance to use them. Please lookout for the changes in the ADT Release Notes.
-Shyam