Hu Dong

Results 18 comments of Hu Dong

> Same comment as in #370, can you please do a quick test with `0.4.0-SNAPSHOT`? NP. will give it a try.

It seems the memory leak problem still exists. The memory usage of `TString.tensorOf` calls grows as the number of iterations increases. **1024 iterations** ![image](https://user-images.githubusercontent.com/3747635/130309496-ba30a8e3-765a-4ce9-87d8-832cff3205f4.png) **65536 iterations** ![image](https://user-images.githubusercontent.com/3747635/130309506-ea6b27bc-975e-4531-93a3-fb79b2c7eec8.png)

I did another test by setting JVM max heap size after upgrading TF java to `0.4.0-SNAPSHOT`. With `-Xmx47m`, 4 iterations can pass while 65536 iterations would cause OOM. ![image](https://user-images.githubusercontent.com/3747635/130312448-e840b9b8-b230-4cc3-bff8-55fcac8ecc7e.png)

Hi, guys! You could retry compiling the project with following suggestions: 1. rename the IDEA sdk from something like "IDEA IU-135.123" to "IDEA". 2. delete line 13 ~ line 15...

Just run into the same problem with `transport='rest'` and `send_message_async`.

Disabling the custom all-reduce functionality with the `--disable-custom-all-reduce` flag resolves the issue. We've tested this successfully with both the `vllm:0.4.1` and `vllm:0.4.2` Docker images, without needing to enable eager mode...

This plugin is not in active development. But PRs are welcome.

Just encountered the same problem after updating it to 0.64.0. However, downgrading to 0.63.0 works for me, without any configuration change.