Background:-
On our site we had a performance problem with the SAP ALE eway when using a single CPU machine. This appeared to be due to a thread race between the send to SAP and the read from the IQ containing the IDOCS. Config options on eway didn't help.
I then tried putting Auto Recovery on for the dedicated IQ that was used by the file input eway and SAP ALE eway for our test. The documentation said this would degrade performance which was why we had not used it before. It sped up our eways thoughput by 80%. This parameter was not there for 4.1 versions of the EGATE.
Question:-
My questions are :- Has anyone else using 4.5.2 had the same experience of Auto Recovery speeding up IQ processing?
Has anyone any information that suggests Auto Recovery may cause problems, if so of what type?
I've onlt had limited experience with EGATE
On our site we had a performance problem with the SAP ALE eway when using a single CPU machine. This appeared to be due to a thread race between the send to SAP and the read from the IQ containing the IDOCS. Config options on eway didn't help.
I then tried putting Auto Recovery on for the dedicated IQ that was used by the file input eway and SAP ALE eway for our test. The documentation said this would degrade performance which was why we had not used it before. It sped up our eways thoughput by 80%. This parameter was not there for 4.1 versions of the EGATE.
Question:-
My questions are :- Has anyone else using 4.5.2 had the same experience of Auto Recovery speeding up IQ processing?
Has anyone any information that suggests Auto Recovery may cause problems, if so of what type?
I've onlt had limited experience with EGATE