Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 11 to 17 of 17 total |
I'm good at finding strange ones. :-( |
Mon, Aug 26 2019 1:32 PM | Permanent Link |
Ian Branch | Same result
|
Mon, Aug 26 2019 1:33 PM | Permanent Link |
Ian Branch | No progress reporting.
No Global I/O buffering. |
Mon, Aug 26 2019 6:11 PM | Permanent Link |
Ian Branch | Hi Team,
Additional test/observations.. 1. I tried the script and Verify in edbmgr. This time I just left it. It too approx 18 minutes but was successful. - Semi-positive. 2. I tried it all again in my app. Timed out waiting for a response from the server, was set at 180 secs. I changed the timeout to 1200secs (20min) and it then succeeded in completing the verify. 3. Ran the App/Verify again immediately and it took less than a sec. 4. Stopped & restarted the server then re-ran the App/verify - took approx 2 secs. Clearly something is happening in the initial Verify..... Ian |
Tue, Aug 27 2019 12:20 AM | Permanent Link |
Raul Team Elevate | On 8/26/2019 6:11 PM, Ian Branch wrote:
> Additional test/observations.. > 1. I tried the script and Verify in edbmgr. This time I just left it. It too approx 18 minutes but was successful. - Semi-positive. > 2. I tried it all again in my app. Timed out waiting for a response from the server, was set at 180 secs. I changed the timeout to 1200secs (20min) and it then succeeded in completing the verify. Progress reporting should help with timeout in general. > 3. Ran the App/Verify again immediately and it took less than a sec. > 4. Stopped & restarted the server then re-ran the App/verify - took approx 2 secs. I know the answer but any chance you are running "structure only" clause in "fast" case and full one "slow" one ? How about full system restart between - just to eliminate OS disk caching ? 2 sec vs 18 min is weird still - Tim would have comment I think . Raul |
Tue, Aug 27 2019 1:56 AM | Permanent Link |
Ian Branch | Raul wrote:
On 8/26/2019 6:11 PM, Ian Branch wrote: > Additional test/observations.. > 1. I tried the script and Verify in edbmgr. This time I just left it. It too approx 18 minutes but was successful. - Semi-positive. > 2. I tried it all again in my app. Timed out waiting for a response from the server, was set at 180 secs. I changed the timeout to 1200secs (20min) and it then succeeded in completing the verify. Progress reporting should help with timeout in general. IB - Hadn't thought about incorporating it att. > 3. Ran the App/Verify again immediately and it took less than a sec. > 4. Stopped & restarted the server then re-ran the App/verify - took approx 2 secs. I know the answer but any chance you are running "structure only" clause in "fast" case and full one "slow" one ? IB - Both the same mode. How about full system restart between - just to eliminate OS disk caching ? IB - Tried that. 2 sec vs 18 min is weird still - Tim would have comment I think . IB - Hopefully. Raul |
Tue, Aug 27 2019 8:38 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Ian
You need to pass this one onto Tim with the data. Roy Lambert |
Tue, Aug 27 2019 6:10 PM | Permanent Link |
Ian Branch | Roy Lambert wrote:
>>You need to pass this one onto Tim with the data. Yup. Will do. Ian |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |