Abundant network traffic between metadata server and management console

[jklaverstijn]

Intermediate update: we have deleted many of the project repositories after careful selection. Going from 320 to 45 made a world of difference. We're not there yet and expect more from our track with tech support, but wanted you to know this.

There's a gotcha: when you do this metadata clients like sasmc can/will get very upset. They start complaining about missing repositories. Probably harmless but very confusing to the users so we moved this to outside office hours. To avoid endless mouseclicking we used a script with sas-delete-repository command line utility with a short sleep between every cycle to keep it light for the metadata server cluster.

Sooo we're in a much better shape now. But the in the track SAS started with questioning the use of project repositories in the first place. Couldn't we just [...]? Really, SAS?

Regards,
-- Jan.

[Kurt_Bremser]

I guess the mechanism for separate repositories was meant to cover something like 2,3,4, maybe 5. Since it was never meant to be used for hundreds of repositories, nobody tested that. Or did not care for performance penalties incurred.

[PaulHomes]

Thanks for providing the update Jan. Purely out of interest, what is the use case for so many project repositories? Is it simply that there are lots of SAS DI Studio users doing change managed updates or are you you using them in another capacity?

[jklaverstijn]

There was no purpose for the 300+ repositories, that's why we managed to
eliminatie so many. But 50+ (and more to come) is for real. We are a big
shop. Real big. And most teams employ change management for their
development process. Our scale is why we use grid manager and clustered and
load balanced everything.