[Improvement]: Display more details in the page of Optimizing->Optimizers

[tcodehuber]

Search before asking

• I have searched in the issues and found no similar issues.

What would you like to be improved?

Now there are only a few of columns displaying in the Tab of Optimizing->Optimizers. IMO, we can show more columns(startTime, touchTime, jobJd etc.) to distinguish the optimizers.

How should we improve?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[XBaith]

Hi @tcodehuber , Consider displaying the optimizer token id on the page so that we can identifier the different optimizer

[tcodehuber]

@XBaith JobId(Optimizer Id) usually contains resourceid. Can it be considered as identifier for different optimizers?

[XBaith]

@XBaith JobId(Optimizer Id) usually contains resourceid. Can it be considered as identifier for different optimizers?

In some scenarios, the resouceid is empty or just a subindex, which I don't think is clear enough

[tcodehuber]

[baiyangtx]

I think it is useful that OptimizerId can distinguish between different optimizer instances, but for Token and Touch Time, it should be used more often to locate the problem, does this need to be displayed on the frontend?

Also, when there is an optimizerId to distinguish between different optimizer instances, it should be possible to cancel the order column, which has no practical meaning.

[tcodehuber]

I think it is useful that OptimizerId can distinguish between different optimizer instances, but for Token and Touch Time, it should be used more often to locate the problem, does this need to be displayed on the frontend?

Also, when there is an optimizerId to distinguish between different optimizer instances, it should be possible to cancel the order column, which has no practical meaning.

Yes, i agree with discarding the order column. Furthermore, touchTime can be used as the active state for users.

[tcodehuber]

@baiyangtx @XBaith Can we discuss whether displaying the Token column in the frontend?

[baiyangtx]

Can we discuss whether displaying the Token column in the frontend?

Is it really necessary to display the token on the frontend, and in what scenarios do you need to know this value? @XBaith

Furthermore, touchTime can be used as the active state for users.

If the optimizer is not active, it will disappear from frontend.

[zhoujinsong]

@tcodehuber @baiyangtx @XBaith
Have we reached a consensus on what content needs to be added to the page?

[tcodehuber]

In my opinion, we can remove token from the frontend.

[XBaith]

If the optimizer is not active, it will disappear from frontend.

Disply the token id can help us to identifier status of optimzier. It would be better if we make it more clear when the optimizer is expired via change the status in the front site. WDYT @baiyangtx ?

[baiyangtx]

Disply the token id can help us to identifier status of optimzier. It would be better if we make it more clear when the optimizer is expired via change the status in the front site.

If you want to see a disconnected optimizer on the page, it's a better idea to display it with status.
I think the token is too low-level information to be displayed on the list page, maybe we can add a detail page, or hover to display some details. WDYT @zhoujinsong @XBaith

[XBaith]

If you want to see a disconnected optimizer on the page, it's a better idea to display it with status.

+1. Currently, AMS optimizer only show the "running" status in the front page, it's a good way to expose more detail for optimizer.

[tcodehuber]