limowang opened a new issue, #2413: URL: https://github.com/apache/incubator-pegasus/issues/2413
PR (https://github.com/apache/incubator-pegasus/pull/1687) introduced a patch to the RocksDB build process, allowing `PORTABLE` to accept not only `0/1` values but also specific CPU architecture. However, the current project only supports `ROCKSDB_PORTABLE` values of `0/1` and does not allow specifying a specific CPU architecture. The build artifacts produced by this project need to be deployed on different customers' machines. If `ROCKSDB_PORTABLE` is set to `0`, the binary can fully utilize the CPU features of the build machine, but it may cause instruction set incompatibility issues when running on customers' machines with different CPUs. If `ROCKSDB_PORTABLE` is set to `1`, the binary becomes portable but cannot fully utilize the performance advantages of the customer's CPU. Therefore, supporting a specific CPU architecture, such as `haswell`, provides a better balance between portability and performance. With this setting, CPU features such as AVX2, SSE4.2, and PCLMUL can be enabled, while most customer machines are still expected to support these instruction sets. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
