Known issues using SWIS APIs?

I have a ticket opened, for excessive CPU/RAM used on servers

It appears that there is a memory leak using massive API/SDK actions (we update custom properties very often).
Scripts are ran from main servers, but impact are on all APE, where solarwinds.informationservice.service consums all the free memory (+8GB), we have to reboot every week before reach 100% ram usage

Could you share the case number with me for that issue?

Sure, here it is : Case # - 00578855

I hope that it was really the SDK and that a patch will be provided, because support close this old ticket (07/2020) with this reason.

Sure, here it is : Case # - 00578855

I hope that it was really the SDK and that a patch will be provided, because support close this old ticket (07/2020) with this reason.

Depending on your environment 8 GB of ram might not be enough for the abuse, i run 32 GB on my primary server.  When you see issues is the common symptom to have the info service eat up all the ram and the system generally becomes slow/unresponsive?  In my experience running into that problem is usually caused by poorly written SWQL queries.  I make at least 10,000 api calls a day to my Orion instance just counting stuff that is external as part of various integrations and reports I do and have experienced no significant memory leak, but we do also reboot our servers weekly as preventative maintenance, 5 min of delayed alerts while we restart in the middle of the night tends to keep our systems up reliably instead of chasing random gremlins at inconvenient times.

Our main server have 32GB RAM (and our 11 APE too), the 8GB is the memory used just by SolarWinds.InformationService.ServiceV3 process.

I just relay support conclusion. I opened the ticket in 07/2020 because of CPU/RAM excessive usage, the process SolarWinds.InformationService.ServiceV3 use all the memory of our servers (main, APE) ; and erl.exe all the CPU

Support analyzed logs, logs logs logs, dumps, dumps, logs, taking months.

Finally, pointing SDK usage, closed the ticket saying that a patch will be provided (??). Are you agreed with support saying that powershell script on main server using sdk can consume all the memory on all our APE too ?  

If this is not the real reason and it was just a trick to close my ticket, it's insane

Last message from the support :

As per our Senior Developer, This is now considered as a major bug in the product which will surely be addressed in the future release but the version has not been identified yet.

With the statement above, This ticket will be tracked internally and since there was no given estimated time of repair, We are now going to archive the case as well.

The last suggestion our Senior Developer had advised was to minimize the action of updating the CustomProperties and we are hoping that it give a sort of improvement.

Please feel free to let us know should you have further clarifications or concerns regarding the subject matter.

(and my swql queries are fine, thanks)

CPU/RAM usage on APE, same thing on 11 APE. Rebooted once a week because of SolarWinds.InformationService.ServiceV3 using all the memory. Sometimes i had to reboot twice a week, when server reach 95% memory used, solarwinds services randomly crash 

last 30 days :

and this is the main server, same thing, erl.exe use a LOT of CPU (12 vcpu), and SolarWinds.InformationService.ServiceV3 use ALL the memory

last 30 days :

and in 24 hours : 

This is being tracked internally and is being prioritized accordingly. It is being tracked as a bug in the product and had been planned for a previous release, however, it did not make it as we adjusted priorities.  High resource utilization is a symptom of the problem, which is reloading of the SWIS schemas on a frequent basis. The root cause of which is the frequency of the changes generated by the script calls to the API which I understand are updating values each time it is executed, even in the absence of any changes to the values. If this is correct, have you considered 1st comparing the values to determine if there is any update needed?

is this resolved? i believe 2 version have been released since last 5 months.