Based on the elements you've shown, I would first recommend reviewing the behavior of the DisputeSubmit.insertDisputeInfo method (for example, by using MapStruct). MapStruct generates a class at compile time, whereas BeanUtils relies on reflection, which makes MapStruct more efficient. Since the code is generated at compile time, potential issues can be detected at that stage rather than at runtime. However, further investigation would be necessary to ensure that there are no other sources of excessive reflection or dynamic class generation in your application.