polyzos commented on issue #1332: URL: https://github.com/apache/fluss/issues/1332#issuecomment-3079117828
How do you think we should approach this? I’m thinking maybe it’s good to document some scenarios we want to test and discuss environment, cluster size etc. Maybe TestContainers make sense? And start a 3 node cluster, setup a few writers per table type that generate x events per second or y number of MB/s and measure different parameters. Test scanners or simulate lookups for x number of concurrent lookups while writing. Test partitioning etc. or things like projections, column pruning or later predicate pushdowns. Overall it should be reusable so we can a way to get adult benchmark and test things throughout releases. Just adding some thoughts here as notes to kickstart the discussion, and happy to help here. -- 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]
