-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client configuration #4
Conversation
@@ -151,6 +156,8 @@ public virtual async Task<Response<PersonalizerRankResult>> RankAsync(Personaliz | |||
} | |||
else | |||
{ | |||
Models.PersonalizerClientProperties result = await ClientConfigurationRestClient.PostAsync(cancellationToken).ConfigureAwait(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Calling the ClientConfigurationClient here instead when isLocalInference is true (these two lines will be moved) just to test the new code is working when RankTest is called. But few things have to be modified while testing for the test case to work. Tested in my local machine and it worked as below.
Standard Output:
InternalId: 86aa7660871843dca1c703400557b71c
StorageBlobUri: BlobURI
LearningMode: 0
Exploration Percentage: 1
initialCommandline: --cb_explore_adf --json --quiet --epsilon 0.0 --first_only --id N/A
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The point of the thick client, is decrease latency. By making a configuration network request on every rank call, the latency is effectively increased. This configuration should also be shared across the entire client, not just the rank call. Consider moving to a wider scope and changing the client configuration to a TTL lazy initialization.
@@ -151,6 +156,8 @@ public virtual async Task<Response<PersonalizerRankResult>> RankAsync(Personaliz | |||
} | |||
else | |||
{ | |||
Models.PersonalizerClientProperties result = await ClientConfigurationRestClient.PostAsync(cancellationToken).ConfigureAwait(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The point of the thick client, is decrease latency. By making a configuration network request on every rank call, the latency is effectively increased. This configuration should also be shared across the entire client, not just the rank call. Consider moving to a wider scope and changing the client configuration to a TTL lazy initialization.
@@ -182,6 +189,8 @@ public virtual async Task<Response<PersonalizerRankResult>> RankAsync(Personaliz | |||
/// <param name="cancellationToken"> The cancellation token to use. </param> | |||
public virtual async Task<Response<PersonalizerRankResult>> RankAsync(IEnumerable<PersonalizerRankableAction> actions, IEnumerable<object> contextFeatures, CancellationToken cancellationToken = default) | |||
{ | |||
Models.PersonalizerClientProperties result = await ClientConfigurationRestClient.PostAsync(cancellationToken).ConfigureAwait(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentioned in the previous comment, this is duplicated logic.
@@ -182,6 +189,8 @@ public virtual async Task<Response<PersonalizerRankResult>> RankAsync(Personaliz | |||
/// <param name="cancellationToken"> The cancellation token to use. </param> | |||
public virtual async Task<Response<PersonalizerRankResult>> RankAsync(IEnumerable<PersonalizerRankableAction> actions, IEnumerable<object> contextFeatures, CancellationToken cancellationToken = default) | |||
{ | |||
Models.PersonalizerClientProperties result = await ClientConfigurationRestClient.PostAsync(cancellationToken).ConfigureAwait(false); | |||
Console.WriteLine("InternalId: " + result.ApplicationID + "\nStorageBlobUri: " + result.ModelBlobUri + "\nLearningMode: " + result.ProtocolVersion + "\nExploration Percentage: " + result.InitialExplorationEpsilon + "\ninitialCommandline: " + result.InitialCommandLine); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not write to console in production code. If something needs to be output, it should be done through a logger. For this particular case, I would suggest removing entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIP: When you want to print the entire object is usually best to use JSON serialization. Console.Write(JsonConvert.SerializeObject(result));
config["appid"] = result.Value.ApplicationID; | ||
|
||
// set up the model | ||
config["model.source"] = result.Value.ModelBlobUri; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be "model.blob.uri"
|
||
// set up the model | ||
config["model.source"] = result.Value.ModelBlobUri; | ||
config["model.vw.initial_command_line"] = result.Value.InitialCommandLine; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be "vw.commandline"
sdk/personalizer/Azure.AI.Personalizer/src/Models/PersonalizerClient.cs
Outdated
Show resolved
Hide resolved
This reverts commit d6df6b5.
…azure-sdk-for-net into ClientConfiguration
|
||
namespace Azure.AI.Personalizer.Models | ||
{ | ||
internal class ClientConfigurationRestClient |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why isn't this class in the generated folder? Rest clients should not be hand written, only extended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As client Post is not part of swagger because of which it's not part of generated. So implemented it outside generated to get client config details
/// <summary> Gets the configuration details for the live model to use </summary> | ||
internal Configuration GetClientConfigurationForLiveModel() | ||
{ | ||
result = new Lazy<Models.PersonalizerClientProperties>(() => ClientConfigurationRestClient.Post()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should have a TTL in case the configuration on the server is updated.
Also, I would suggest the Lazy TTL be managed by the caller, not inside this method. In other words, the caller should use Lazy.
result = new Lazy<Models.PersonalizerClientProperties>(() => ClientConfigurationRestClient.Post()); | ||
Configuration config = new Configuration(); | ||
// configure the personalizer loop | ||
config["appid"] = result.Value.ApplicationID; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of call result.Value
half a dozen times, please use a temporary reference.
{ | ||
internal partial class PersonalizerClientProperties | ||
{ | ||
internal static PersonalizerClientProperties DeserializePersonalizerServiceProperties(JsonElement element) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain why we need a custom deserializer instead of using JsonSerializer.Deserialize<PersonalizerClientProperties>(string)
?
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
Draft
mode if it is:General Guidelines and Best Practices
Testing Guidelines
SDK Generation Guidelines
*.csproj
andAssemblyInfo.cs
files have been updated with the new version of the SDK. Please double check nuget.org current release version.Additional management plane SDK specific contribution checklist:
Note: Only applies to
Microsoft.Azure.Management.[RP]
orAzure.ResourceManager.[RP]
Management plane SDK Troubleshooting
If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add
new service
label and/or contact assigned reviewer.If the check fails at the
Verify Code Generation
step, please ensure:generate.ps1/cmd
to generate this PR instead of callingautorest
directly.Please pay attention to the @microsoft.csharp version output after running
generate.ps1
. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.Note: We have recently updated the PSH module called by
generate.ps1
to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.