Is your feature request related to a problem? Please describe.
The timestamp used in chat responses seems to be when the response is initiated, not when complete. For example, the timestamp when interrogating a document matches the prompt timestamp even though the actual response content takes several minutes to generate given hardware constraints. This makes it difficult to benchmark.
Describe the solution you'd like
Have a timestamp showing the completed response time
Describe alternatives you've considered
Counting in my head
Additional context
None
Originally created by @sengenbe on GitHub (Apr 10, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1493
**Is your feature request related to a problem? Please describe.**
The timestamp used in chat responses seems to be when the response is initiated, not when complete. For example, the timestamp when interrogating a document matches the prompt timestamp even though the actual response content takes several minutes to generate given hardware constraints. This makes it difficult to benchmark.
**Describe the solution you'd like**
Have a timestamp showing the completed response time
**Describe alternatives you've considered**
Counting in my head
**Additional context**
None
Edit: To be even more direct, ideally the reponse would provide the length of time it took to generate the response
<!-- gh-comment-id:2048170721 -->
@sengenbe commented on GitHub (Apr 10, 2024):
Edit: To be even more direct, ideally the reponse would provide the length of time it took to generate the response
Edit: To be even more direct, ideally the reponse would provide the length of time it took to generate the response
It does:
I realize it is extra work but can you not take the initiation timestamp and add the duration to get the completion timestamp?
<!-- gh-comment-id:2048172219 -->
@justinh-rahb commented on GitHub (Apr 10, 2024):
> Edit: To be even more direct, ideally the reponse would provide the length of time it took to generate the response
It does:

I realize it is extra work but can you not take the initiation timestamp and add the duration to get the completion timestamp?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @sengenbe on GitHub (Apr 10, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1493
Is your feature request related to a problem? Please describe.
The timestamp used in chat responses seems to be when the response is initiated, not when complete. For example, the timestamp when interrogating a document matches the prompt timestamp even though the actual response content takes several minutes to generate given hardware constraints. This makes it difficult to benchmark.
Describe the solution you'd like
Have a timestamp showing the completed response time
Describe alternatives you've considered
Counting in my head
Additional context
None
@sengenbe commented on GitHub (Apr 10, 2024):
Edit: To be even more direct, ideally the reponse would provide the length of time it took to generate the response
@justinh-rahb commented on GitHub (Apr 10, 2024):
It does:
I realize it is extra work but can you not take the initiation timestamp and add the duration to get the completion timestamp?