-
Notifications
You must be signed in to change notification settings - Fork 637
packing似乎和lazy_encode参数是冲突的? #4054
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
Comments
可以使用streaming的 |
@Jintao-Huang 感谢回复,请问如何确定packing是生效的。streaming状态下似乎无法通过每个epoch的step数来判断。 |
是的,未来会加上一个参数,如果超过max_epochs,会强制结束并保存权重 |
似乎比较好的方式是: |
有shell嘛 |
|
多模态模型 数据集在本地嘛 |
你试试升级一下swift 看看能否解决问题 dataloader这里应该重构了 |
数据我已经都转成字符串格式了,所以是单模太。 |
ms-swift/swift/llm/data_loader.py Line 57 in 49394e1
升级一下swift试试吧 |
@Jintao-Huang 感谢大佬假期还解答问题,目前更换到3.4版本,训练效率确实提高了2.5倍左右。gpu利用率也正常了。 |
更新到最新的版本后出现了新的问题,在执行到evaluation的步骤时出现。 |
fixed |
Describe the bug
packing操作和lazy_encode参数是冲突的吗?貌似开启lazy_encode后packing会失效。具体是通过每个epoch需要的训练步数判断出来的。
另外是否packing也会和steaming参数冲突,我需要如何验证packing是正常开启的?
Your hardware and system info
ms_swift==3.2.2
The text was updated successfully, but these errors were encountered: