Hi Narasimha, there are many factors that affect the performance of a service.
Perhaps, the most common factors are: number of CPUs & Cores per CPU, amount of memory allocated to VSE, is VSE logging turned off, does the system use an enterprise DBMS other than the Derby DB that ships with the product, how many other services are involved in the performance test (i.e., amount of concurrent activity on the VSE) and what customizations (i.e., additional steps, XPath, custom logic, etc.) may exist within the service.
It is highly likely that 100 TPS is achievable. We have executed significantly higher TPS volumes than that for numerous customers.
The link below might help you with some tuning steps for the VSE.
Please disregard the sections on Java GC Tuning. I have only seen one Use Case where GC tuning was necessary and those settings were made to a DevTest version that is no longer supported.
Tech Tips: DevTest Performance Tuning