can you tell us about your implementation?
• which version of the java SDK are you using? we released 0.8.1 a couple weeks ago and it has a minor fix that may have impacted performance. if you are on an earlier version, try updating and seeing if that helps.
• what framework are you using, if any (e.g. spring, micronaut, ktor, etc.)
• can you share your features URL (if public, unencrypted)? i want to see if there may be issues due to the size of the features JSON.
• can you share the code you're using for networking, e.g. your implementation of the GBFeaturesRepository or where you're making the calls manually
• have you done any profiling to pinpoint the cause of the problem? e.g. is it in the networking implementation, or in the feature or experiment evaluation?
previously a user mentioned that the example in our docs (which uses
<http://java.net|java.net>.http.HttpClient
) is not performant in spring. if using spring, did you look at the spring examples? there's several implementations in
here (e.g. using the GBFeaturesRepository class, or making calls with your own networking implementation). there may also be a better way to do the same thing in spring or your framework of choice—the repository class is meant to be framework agnostic.
