Re: Transaction slowness
Date: Fri, 15 Oct 2021 16:05:39 +0100
Message-ID: <CAGtsp8ktjhW8M+W5DS1ZHa-Y28xinRcARZibcM2Z5pnOEgYeTg_at_mail.gmail.com>
I don't know if it's relevant to the specific technology, but I like the
idea suggested by Rajeev.
One thing I'd check is whether that time spent in SQL*Net message from
client is a small number of long waits or a very large number of small
waits, and how much of the time also turns out to be "SQL*Net more data to
client"; and what happens at the database just before the wait for client.
Regards
On Fri, 15 Oct 2021 at 02:47, Amit Saroha <eramitsaroha_at_gmail.com> wrote:
> Hi Rajeev,
Jonathan Lewis
>
> Thanks for the response.
>
> The mobile devices are using Oracle MWA for WMS operations accessing EBS
> database. This is Java based mobile app framework.
>
>
> Regards,
> Amit
>
> On Thu, Oct 14, 2021 at 9:38 PM Rajeev Prabhakar <rprabha01_at_gmail.com>
> wrote:
>
>> Amit,
>>
>> I could be way off the mark, but, just wondering if
>> this the case of jsp files getting created/compiled
>> on the first time invocation by the App given that
>> this is done via mobile device ?
>>
>> The subsequent calls could be utilizing the cached /
>> compiled jsp files, so, are faster…
>>
>> If not, perhaps you could give some background on
>> the interface/language being used by the App ?
>>
>> My point, unless you have already ruled it out, there
>> could be variables/factors outside of the database
>> layer contributing to the initial sluggishness..
>>
>> Rajeev
>>
>> On Oct 14, 2021 at 6:55 PM, <Amit Saroha <eramitsaroha_at_gmail.com>> wrote:
>>
>> Hello All,
>>
>> We are facing a weird slowness in database response to users. The
>> situation is - Warehouse operators are unloading trucks on the dock and
>> moving material to locators. When they are doing the activity, they have to
>> scan barcodes on a mobile device and keep moving items in locators to clean
>> up the dock to make a way for another truck for unloading material. When
>> the user is doing the first transaction on a mobile device, it takes 5-10
>> minutes, but the next transactions are complete in 5-10 seconds. The delay
>> in first transaction completion is causing an overall delay in warehouse
>> work efficiency.
>>
>> 10046 traces enabled on the session while doing the first transaction,
>> which takes 5-10 minutes, revealed that over 80% of the time is going in
>> SQL*NET message from the client. Trace for the next sessions also shows the
>> same event is top, but the transaction completes within 10 seconds.
>>
>> We don’t understand why the first transaction is taking time, and the
>> next is not so struggling to fix the issue. We also don’t want to conclude
>> it as a network issue because subsequent transactions are quick.
>>
>> We would appreciate it if any of you could please tell us if anyone has
>> observed the same situation and what we can do to rectify such behavior?
>>
>> Thank you in advance for your inputs.
>>
>>
>> Best Regards,
>> AMIT
>>
>> --
> Best Regards,
> AMIT SAROHA
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Oct 15 2021 - 17:05:39 CEST