See above EDITED section for some more context. We do an initial pull from OneStream using the GetMembersUsingFilter in which we get the MemberInfo Object and use IDs from there. That function is very fast. The slow part is in retrieving and updating the Text Fields.
Depending on which way I tried, calling the Members.GetMemberInfo or the Metadata.Member with the includeProperties flag set to True takes the nearly 2 seconds. I tried using GetUDProperties or using UD.Text() both and all were hit some where with a 2 second cost.
OneStream EmployeeI wonder if there is some corruption somewhere, like a table that lost its indexes, or a lot of orphans, or a hierarchy that is particularly bonkers. Maybe some optimization could be done at the db level, logging the queries to determine where the slowdown is (you can use ReadMemberPropertiesNoCache to ensure you're hitting the database every time).
In any case, if the api really is that slow, you can speed things up by doing the reading part via SQL directly on the MemberProperty table (you just have to figure out the PropertyID for Text5, but that should be easy enough), and then use the api only for the specific members that need changing.
