Skip to content
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

How does Weights json file work? #127

Open
jdini76 opened this issue Sep 19, 2022 · 3 comments
Open

How does Weights json file work? #127

jdini76 opened this issue Sep 19, 2022 · 3 comments

Comments

@jdini76
Copy link

jdini76 commented Sep 19, 2022

Could someone provide an example of how the weights json file is supposed to be formatted and how it works? There are no examples in the project or any documentation on it.

@jdini76
Copy link
Author

jdini76 commented Sep 19, 2022

I figured it out. This response is for others wondering. The weights json file is automatically created/updated after a 100% successful run. So it might be best to run through your scripts with a single thread to generate an initial weights json file. Then, in corresponding executions it will read the weights file to properly distribute the specs across the threads.

@Infurnia-Nitin-Upadhyaya

I figured it out. This response is for others wondering. The weights json file is automatically created/updated after a 100% successful run. So it might be best to run through your scripts with a single thread to generate an initial weights json file. Then, in corresponding executions it will read the weights file to properly distribute the specs across the threads.

@jdini76 could you share me your npm script command with weight json and how does the weight json file look like , bit confused need help

@lems3
Copy link

lems3 commented Apr 3, 2023

I figured it out. This response is for others wondering. The weights json file is automatically created/updated after a 100% successful run. So it might be best to run through your scripts with a single thread to generate an initial weights json file. Then, in corresponding executions it will read the weights file to properly distribute the specs across the threads.

After a couple of test here, I found out that, for us at least with 3 threads, the file generated after a run with all 3 threads is better than a file generated with only 1 thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants