cjcchen commented on issue #169: URL: https://github.com/apache/incubator-resilientdb/issues/169#issuecomment-2598957135
Hi Shubo, I saw you used c5a.xlarge which only contains 8GB mem. The memory is not enough as the performance tool suit will generate a large amount of requests. You can reduce the number of requests by changing the number here: https://github.com/apache/incubator-resilientdb/blob/master/platform/consensus/ordering/pbft/performance_manager.cpp#L111 Like 60000000 to 2000000. Hope this can help you. Thanks, Junchao On Fri, Jan 17, 2025 at 9:18 PM Shubo Peng ***@***.***> wrote: > Hi developer, I'm having troubles in *testing PBFT performance*. > > I launched 5 AWS instances as nodes for resdb. While running the command: > > *./performance/pbft_performance.sh config/kv_performance_server.conf* > > to test performance, I encountered the following issue: > > 2025-01-17.21-13-27.png (view on web) > <https://github.com/user-attachments/assets/0e04601e-5d71-41e7-8d13-9ff0c91f6a1b> > > During the execution of the script, the client node suddenly disconnects, > resulting in an incorrect number of nodes being counted when calculating > the results. > > 2025-01-17.21-14-31.png (view on web) > <https://github.com/user-attachments/assets/b02b50de-1406-4012-8b54-0bd409a10045> > > I checked the AWS console for the affected node’s resource usage (the > instance type is c5a.xlarge), and here are the observations: > > - CPU usage peaked at 37%. > - Network traffic reached a maximum of 110M/220M (in/out). > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-resilientdb/issues/169>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA4YYLTIRKOCAIXWEHRNB5L2LD7MFAVCNFSM6AAAAABVL5CM46VHI2DSMVQWIX3LMV43ASLTON2WKOZSG44TKNBWGYYDMNY> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- 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]
