-
Notifications
You must be signed in to change notification settings - Fork 43
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
Prototype profiler object serialization using JSON #343
Comments
@ThreeMonth03 is working on this issue with PR #323. |
@ThreeMonth03 plans to make the next review for PR #323 ready by 5th June. |
#323 is merged. We should start to exercise the data for analyzing performance to find out how useful it is and how to improve the design (of the profiler and the serialization). |
@ThreeMonth03 Since #372 and #377, the general JSON parser, is merged, could you revise |
Thank's for your contribution, I will trace the implementation and revise the |
@ThreeMonth03 @q40603 @tigercosmos do we have anything needed for this issue or need any further PR? |
Yes, I will. I will make a pr after issue382 |
@ThreeMonth03 Do we have any work left for this issue? |
I think I should expose more class members for serializer and implement the deserializer, but I'm writing the notes for the newcomers. |
No problem. I added the two tasks in the issue description. This issue remains open to track them. |
This issue derives from #302.
Develop a helper class or some helper classes to serialize the
CallProfile
object used for recording the profile data (in memory). Remarks:There should be a capability to deserialize the data back to
CallProfile
. We may use this issue to track the deserialization, or use a different issue.The text was updated successfully, but these errors were encountered: