Failed to build simulator app - docker engine crashed

Open Jeffwan opened this issue 1 year ago • 4 comments

🚀 Feature Description and Motivation

I feel this process has be to improved for easy development

Use Case

No response

Proposed Solution

No response

Dec 07 '24 08:12 Jeffwan

It may be because the profiling may take too long. My profiling time is around 500s.

Dec 09 '24 07:12 zhangjyr

I discussed the priority of this issue with Jingyuan and here are our thoughts: The Vidur simulator is mainly for local development. In production, we will be using real GPU profiles instead of the Vidur simulator’s simulated profiles. Users will never need to run the docker-build-simulator command in production (this issue). Given this, we might want to address this issue in the future. Please let us know your thoughts. @Jeffwan

Dec 10 '24 20:12 nwangfw

As we discussed in the previous comment, we can close this issue for now. We will not use Vidur simulator to generate profile in production environment. @Jeffwan.

Dec 27 '24 19:12 nwangfw

@nwangfw Please document the steps to build vidur based container (for heterogenous feature only) and make sure it won't break. I will remove this from v0.2.0 release but keep this open since the development flow is not 100% fixed, seems we will still encounter such issue

Jan 06 '25 19:01 Jeffwan