fandreuz opened a new issue, #13553: URL: https://github.com/apache/skywalking/issues/13553
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component Java Agent (apache/skywalking-java) ### What happened I'm getting `JFR_UPLOAD_FILE_TOO_LARGE_ERROR` as a result to my Async-Profiler tasks. I'm profiling [Renaissance](https://github.com/renaissance-benchmarks/renaissance) `all` benchmark. I set a large value for `SW_RECEIVER_ASYNC_PROFILER_JFR_MAX_SIZE` (hundreds of GBs just to be sure), so this is quite unexpected. The problem happens frequently with `duration=15mins`, never with `duration=5mins`. Selecting other parallel profiling modes (alloc, lock, wall) gives the same problem even with a 5mins profiling window. ### What you expected to happen This behavior is unexpected since the JFR I get from plain Async-Profiler is less than 100MBs. ### How to reproduce - Launch [Renaissance](https://github.com/renaissance-benchmarks/renaissance) `all` benchmark - Create an Async-Profiler task in SkyWalking OAP server - Select any CPU sampling mode (`CPU`, `ITIMER` or `CTIMER`) - Select 15mins duration - Start the task ### Anything else I started the OAP server with a slightly modified `quickstart-docker.sh` to set `SW_RECEIVER_ASYNC_PROFILER_JFR_MAX_SIZE` from an `env-file`: ``` docker compose -f "$temp_dir/docker-compose.yml" \ --project-name=skywalking-quickstart \ --profile=$SW_STORAGE \ --env-file=/home/fandreuz/sky-test/env \ up \ --detach=${DETACHED:-true} \ --wait ``` `/home/fandreuz/sky-test/env`: ``` SW_RECEIVER_ASYNC_PROFILER_JFR_MAX_SIZE=1000524288000000000 ``` ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
