sql命令行执行也是很快 就是传参数很慢
Comment From: github-actions[bot]
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨
Comment From: ivila
建议检查一下MySQL服务端的配置以及资源信息。 然后可以看看Prepared Statement相关的内容。 我觉得可能是你的MySQL服务端处理Prepared Statement时效率较低导致。
Comment From: github-actions[bot]
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨
Comment From: zobx
很奇怪 就这个59640有问题 别的都很快
Comment From: github-actions[bot]
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨
Comment From: ivila
@zobx 还是建议你去检查一下你的MySQL Server，比如你可以直接用命令行连接，打开对应连接的profile（set profiling=1）自行测试（分别看看你直接执行和使用prepared statement执行的区别）。 可以看看这几个方向： 1，com_id的数据类型是什么？ 2，你建立的索引是怎么样的？ 我看到你这里有过滤后再order by，如果你数据量大的话，可能是正好撞到了MySQL的优化器犯蠢了，某些情况下选择了全表扫描。这种时候你只能是force index强制使用索引了。
Comment From: github-actions[bot]
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨