简体   繁体   English

WSO2 DSS中的高响应时间

[英]High response time in WSO2 DSS

I have created a simple data service using WSO2 DSS for the following simple query. 我已经使用WSO2 DSS为以下简单查询创建了简单数据服务。

"SELECT * FROM EMP_VIEW" “选择*来自EMP_VIEW”

"EMP_VIEW" is having around 45 columns and 8500 entries(tuples). “ EMP_VIEW”大约有45列和8500个条目(元组)。 My DB instance is Oracle 11g Enterprise edition & i'm using ojdbc6.jar as the driver. 我的数据库实例是Oracle 11g企业版,我正在使用ojdbc6.jar作为驱动程序。 Due to some reason Data Service takes around 14 mins to get the response once I try it in SoapUI. 由于某种原因,一旦在SoapUI中尝试了数据服务,数据服务大约需要14分钟才能获得响应。 But the same query takes around 14 or less seconds to retrieve all the records in Oracle SQL Developer/ Eclipse database explorer. 但是,相同的查询大约需要14秒或更短的时间才能检索Oracle SQL Developer / Eclipse数据库浏览器中的所有记录。

Any idea why it's taking high response time? 知道为什么要花这么长的响应时间吗?

Not an answer but potential direction in order to get to an answer. 不是答案,而是获得答案的潜在方向。

There may be multiple factors at play here. 这里可能有多种因素在起作用。 You have proven that the Oracle side is working well (assuming the 14s response time is acceptable). 您已经证明Oracle方面运行良好(假设14s的响应时间是可以接受的)。

You mention that SOAPUI takes considerable time. 您提到SOAPUI需要花费大量时间。 This could be a SOAPUI problem where it is waiting for all results to be returned (time taken) and then building a full display (more time taken) before showing the full result. 这可能是SOAPUI问题,它正在等待所有结果返回(花费时间),然后在显示完整结果之前构建完整显示(花费更多时间)。

The Oracle Dev tool could be faster at showing results since it may not be; Oracle Dev工具显示结果的速度可能更快,因为它可能不是。 waiting for the full result set and/or taking much time to build the display. 等待完整的结果集和/或花费大量时间来构建显示。

Keep in mind that DSS is taking the SQL result and placing XML, that in itself may add some time but I suspect the SOAPUI tool is taking a significant amount of time to decode the XML and place on your screen. 请记住,DSS正在获取SQL结果并放置XML,这本身可能会花费一些时间,但是我怀疑SOAPUI工具会花费大量时间来解码XML并将其放置在屏幕上。

To further narrow down the problem I suggest you use another tool 1. possibly the TRYIT tool from DSS and see what type of timing it gets for the same calls. 为了进一步缩小问题的范围,我建议您使用另一种工具1.可能是DSS的TRYIT工具,并查看相同呼叫获得的计时类型。 2. write a small client c# / java etc and measure that actual time between your request and the response. 2.编写一个小型客户端c#/ java等,并测量您的请求和响应之间的实际时间。 This will definitely tell you how long DSS is taking versus how long it takes for the client to form a display. 这肯定会告诉您DSS需要花费多长时间以及客户端形成显示需要多长时间。

Please do post your results as this type of information is definitely helpful to others. 请发布您的结果,因为此类信息对其他人肯定有帮助。

As per my understandings and observations, SOAP UI waits till whole message receive. 根据我的理解和观察,SOAP UI一直等到接收到整个消息为止。 therefore that much of time will spent. 因此将花费大量时间。 but when you try curl, you can find less seconds to generate the response. 但是当您尝试卷曲时,可以花更少的时间来生成响应。

I tried curl to receive 2MB messages with streaming enabled DSS service, The response was generated within less than one second. 我尝试使用curl在启用了流式传输的DSS服务的情况下接收2MB消息,该响应是在不到一秒钟的时间内生成的。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM