What are the main differences between the Thick/Thin clients in Oracle Application Test Suite (OATS)
edited Feb 9, 2009 7:00PM in Managing Applications using Enterprise Manager (MOSC) 5 commentsAnswered
I'm currently experimenting with user defined tests within e-Tester and have found that I need to use the "Thick Client" (Java Client) in e-Load in order to get my user defined tests to work. This got me thinking about the pros'n'cons of each client. I was wondering what people's experiences have been using each client. Presumably the thin client is a lot more efficient for large volume tests but for the time being we are only using relatively low numbers of VUs so I'm guessing either will do.
What works well?
What doesn't work so well?
What are the drawback to using the Thick Client (e.g. memory usage)?
0