I have set up a Hyperledger Fabric network with the following configuration:

2 Peer Organizations
3 Orderer Organizations
1 Certificate Authority

The network is deployed on Kubernetes using the Hyperledger Fabric operator. The peers have a CPU limit of 1 CPU each. My current performance metrics are:

Write Transactions: ~3 seconds
Read Transactions: ~0.4 seconds

What I Have Tried:
Increased Resource Limits: I increased the CPU and memory limits for the peers and orderers, but observed no significant performance improvement.
Tuning Batch Timeout and Batch Size: I experimented with different values for batchTimeout and maxMessageCount in the ordering service configuration, but again, there was no noticeable difference.

My Question:
What are the recommended steps or configurations to decrease the write transaction time in a Hyperledger Fabric network? :

Any specific Kubernetes configurations that might help improve write performance.
Optimal resource allocation for peers and orderers.
Additional Hyperledger Fabric parameters that can be tuned for better performance.
Best practices for setting up Hyperledger Fabric on Kubernetes to ensure efficient transaction processing.
Additional Information:
The network setup uses the Hyperledger Fabric operator for Kubernetes.
The performance bottleneck appears to be in the write transactions, as read transactions are relatively fast.
Any insights or suggestions to help reduce the write transaction time ????