I have conducted an analysis comparing the import speeds of vouchers both locally (where both Tally and the vouchers are stored on a local system) and over the network (using Tally over the network and accessing vouchers from a network path). The results of the analysis are as follows: Are there any methods or techniques to enhance the speed of importing vouchers in Tally? This could include adjusting Tally settings, modifying configuration files, or optimizing XML requests to improve performance. Also please confirm if these timings are accurate or if they exceed the expected duration. If the import process takes longer than expected, kindly suggest what the recommended estimated time should be?
In general, creating a simple voucher in local environment takes less than 100 ms for me (It depends on factors like ram and cpu also) moreover, if you want suggestions regarding improving your current process, it's not possible here. as one need understanding of current process to suggest improvements.
Over the network, Increasing speed isn't very much possible because We just can't do much changes but Still we can do some changes to default code to increase speed by maybe 10-20% but not too much. Importing through TDL speed can be increased depending upon the code structure and data structure
Use Tally Server if justified. It is not throttled. Find what is new or modified. TDL functions like 'NumItems' come to mind. Collections (with minimum tags) are better than built-in Report / Data even if initialized.
I am using below xml request for importing voucher Code: <?xml version="1.0" ?> <ENVELOPE> <HEADER> <TALLYREQUEST>Import Data</TALLYREQUEST> </HEADER> <BODY> <IMPORTDATA> <REQUESTDESC> <REPORTNAME>Vouchers</REPORTNAME> <STATICVARIABLES> <SVCURRENTCOMPANY>XYZ</SVCURRENTCOMPANY> </STATICVARIABLES> </REQUESTDESC> <REQUESTDATA> <TALLYMESSAGE xmlns:UDF="TallyUDF"> <VOUCHER REMOTEID="a**************************z" VCHTYPE="7"ACTION="Create"> <BANKERSDATE.LIST> <BANKERSDATE>0</BANKERSDATE> </BANKERSDATE.LIST> <DATE>20220330</DATE> <NARRATION>abc</NARRATION> <VOUCHERTYPENAME>Payment</VOUCHERTYPENAME> <VOUCHERNUMBER>0</VOUCHERNUMBER> <PARTYLEDGERNAME>A Bank</PARTYLEDGERNAME> <EFFECTIVEDATE>20220330</EFFECTIVEDATE> <ALLLEDGERENTRIES.LIST> <LEDGERNAME>Drawings</LEDGERNAME> <ISDEEMEDPOSITIVE>YES</ISDEEMEDPOSITIVE> <AMOUNT>-2500</AMOUNT> </ALLLEDGERENTRIES.LIST> <ALLLEDGERENTRIES.LIST> <LEDGERNAME>A Bank</LEDGERNAME> <ISDEEMEDPOSITIVE>NO</ISDEEMEDPOSITIVE> <AMOUNT>2500</AMOUNT> </ALLLEDGERENTRIES.LIST> </VOUCHER> </TALLYMESSAGE> </REQUESTDATA> </IMPORTDATA> </BODY> </ENVELOPE>
Posting vouchers individually you get feedback on each one of them. Combining them in one Xml you loose that but gain on network round trip (number of postings). Only if you have full control on posted data it is justified, not to be used with external data.
if after one request the next request come before some interval of time Tally throttles. Or Is Tally using a different protocol,? Or will multi threaded approach work ? If Tally serializes all requests then that will not bring much speed.
