RE: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111725
interpreted = N
texte = This is a multi-part message in MIME format. ------=_NextPart_000_055C_01D01295.8C72DF70 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Matt, =20 The browsers I have used are IE8, IE10 and Chrome. The IE browser times = out first followed by Chrome which takes twice as long. Database size of = 70,000 records no issue =E2=80=A6.we are cleaning up 200,000+ = =E2=80=A6..it has grown and will continue to grow at a rate of 1000 = records a month. =20 I have done some research and it thought it was the =E2=80=9CConnection = Keep Alive=E2=80=9D settings, both on the browser and server, but no = such luck. Anyway =E2=80=A6.it looks like batching it up using smaller = sizes is probably the best way to go. Sigh =E2=80=A6..was hoping to get = lazy. =20 Cheers and thanks for the help =E2=80=A6.TDn =20 From: Psi Prime Inc, Matthew A Perosi [mailto:matt@psiprime.com]=20 Sent: Sunday, December 07, 2014 22:34 To: talk@webdna.us Subject: Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA = Operations =20 Terry, What browser are you using? For many years I've been using the same steps to batch through up to = 70,000 records at a time. Processing that many records takes a few = hours and my browser never timed out. Although, I do find it easier to = batch through 9000 records at a time because the results page will = return in at most, 20 minutes. I admit that I have not tried my batch routine since upgrading to the = latest version of Firefox and Chrome. I'm hoping your experience isn't = related to a new browser version. If it's not related to a new browser version, then I wonder if it's = related to a setting on your computer or on the web server. Oh, another thought... I use Webmin all the time to process my server = backups. Those never time out and they always take more than 3 hours. -Matt On 12/6/2014 8:50 PM, Terry Nair wrote: Hi All, =20 Every end of the month, we clean up our entire membership database and = reset earn points, besides other parameters based on computational = norms. This is processed using WebDNA and we have been doing this = without issue for years. Once the lengthy process, initiated via a = browser url link is initiated, it may take anywhere from 8 to 10 minutes = before the "It is done" page is returned ....i.e. end of the process. =20 Well, our database have grown so large that now ....it is taking 15 = minutes to complete the process. WebDNA is not an issue because we can = see it happily doing its thing but ....the browser which is waiting for = the return page ....times out. I need to get the browser response page = back so as to know when to begin the next phase. Right now, when the = browser times out ....I remote into the server and check the Task = Manager which tells me when WebDNA has done its thing. Not elegant but = it works. =20 Breaking up the DB into smaller chunks to be processed separately is = one way to go ....however, was wondering if any of you guys can suggest = a better way of doing this ....getting the response I need when the job = is done. Being informed via SMS or email is not an option. =20 Thank for the assist folks. =20 Cheers Terry Nair =20 =20 --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us=20 --=20 Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com =20 Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 =20 Direct: 888.872.0274 Fax: 888.488.5924 =20 http://www.perosi.com --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us ------=_NextPart_000_055C_01D01295.8C72DF70 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

= Hi Matt,

=  

= The browsers I have used are IE8, IE10 and Chrome. The IE browser times = out first followed by Chrome which takes twice as long. Database size of = 70,000 records no issue =E2=80=A6.we are cleaning up 200,000+ = =E2=80=A6..it has grown and will continue to grow at a rate of 1000 = records a month.

=  

= I have done some research and it thought it was the =E2=80=9CConnection = Keep Alive=E2=80=9D settings, both on the browser and server, but no = such luck. Anyway =E2=80=A6.it looks like batching it up using smaller = sizes is probably the best way to go. Sigh =E2=80=A6..was hoping to get = lazy.

=  

= Cheers and thanks for the help =E2=80=A6.TDn

=  

From: Psi Prime Inc, Matthew A Perosi [mailto:matt@psiprime.com] =
Sent: Sunday, December 07, 2014 22:34
To: = talk@webdna.us
Subject: Re: [WebDNA] Circumnavigate Browser = Timeout On Lengthy WebDNA Operations

 

Terry,

What browser are you using?

For = many years I've been using the same steps to batch through up to 70,000 = records at a time.  Processing that many records takes a few hours = and my browser never timed out.  Although, I do find it easier to = batch through 9000 records at a time because the results page will = return in at most, 20 minutes.

I admit that I have not tried my = batch routine since upgrading to the latest version of Firefox and = Chrome.  I'm hoping your experience isn't related to a new browser = version.

If it's not related to a new browser version, then I = wonder if it's related to a setting on your computer or on the web = server.

Oh, another thought... I use Webmin all the time to = process my server backups.  Those never time out and they always = take more than 3 hours.

-Matt

On 12/6/2014 8:50 PM, Terry = Nair wrote:

Hi All,

 

Every = end of the month, we clean up our entire membership database and reset = earn points, besides other parameters based on computational norms. This = is processed using WebDNA and we have been doing this without issue for = years. Once the lengthy process, initiated via a browser url link is = initiated, it may take anywhere from 8 to 10 minutes before the "It = is done" page is returned ....i.e. end of the = process.

 

Well, our database have grown so large that now = ....it is taking 15 minutes to complete the process. WebDNA is not an = issue because we can see it happily doing its thing but ....the browser = which is waiting for the return page ....times out.  I need to get = the browser response page back so as to know when to begin the next = phase. Right now, when the browser times out ....I remote into the = server and check the Task Manager which tells me when WebDNA has done = its thing. Not elegant but it works.

 

Breaking up the DB into smaller chunks to be = processed separately  is one way to go ....however, was wondering = if any of you guys can suggest a better way of doing this ....getting = the response I need when the job is done. Being informed via SMS or = email is not an option.

 

Thank = for the assist folks.

 

Cheers = Terry Nair

 

=  

-------------------------------------------------------= -- This message is sent to you because you are subscribed to the mailing = list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/= list/talk@webdna.us Bug Reporting: support@webdna.us =




-- =
Matthew A Perosi
Corporate =Consultant
Mobile Marketing =Expert
Senior Web =Developer
SEO Analyst & =Educator
matt@psiprime.com
<= pre> 
Psi Prime, Inc.
323 =Union Blvd.
Totowa, NJ =07512
 
Direct:=C2=A0 =888.872.0274
Fax:=C2=A0=C2=A0=C2=A0=C2=A0 =888.488.5924
 
http://www.perosi.com
=

----------------------------------------------= ----------- This message is sent to you because you are subscribed to = the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/= list/talk@webdna.us Bug Reporting: support@webdna.us=

------=_NextPart_000_055C_01D01295.8C72DF70-- Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations ("Terry Nair" 2014)
  2. Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations (Steve Raslevich 2014)
  3. Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations ("Psi Prime Inc, Matthew A Perosi " 2014)
  4. RE: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations ("Terry Nair" 2014)
  5. Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA Operations (Steve Raslevich 2014)
This is a multi-part message in MIME format. ------=_NextPart_000_055C_01D01295.8C72DF70 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Matt, =20 The browsers I have used are IE8, IE10 and Chrome. The IE browser times = out first followed by Chrome which takes twice as long. Database size of = 70,000 records no issue =E2=80=A6.we are cleaning up 200,000+ = =E2=80=A6..it has grown and will continue to grow at a rate of 1000 = records a month. =20 I have done some research and it thought it was the =E2=80=9CConnection = Keep Alive=E2=80=9D settings, both on the browser and server, but no = such luck. Anyway =E2=80=A6.it looks like batching it up using smaller = sizes is probably the best way to go. Sigh =E2=80=A6..was hoping to get = lazy. =20 Cheers and thanks for the help =E2=80=A6.TDn =20 From: Psi Prime Inc, Matthew A Perosi [mailto:matt@psiprime.com]=20 Sent: Sunday, December 07, 2014 22:34 To: talk@webdna.us Subject: Re: [WebDNA] Circumnavigate Browser Timeout On Lengthy WebDNA = Operations =20 Terry, What browser are you using? For many years I've been using the same steps to batch through up to = 70,000 records at a time. Processing that many records takes a few = hours and my browser never timed out. Although, I do find it easier to = batch through 9000 records at a time because the results page will = return in at most, 20 minutes. I admit that I have not tried my batch routine since upgrading to the = latest version of Firefox and Chrome. I'm hoping your experience isn't = related to a new browser version. If it's not related to a new browser version, then I wonder if it's = related to a setting on your computer or on the web server. Oh, another thought... I use Webmin all the time to process my server = backups. Those never time out and they always take more than 3 hours. -Matt On 12/6/2014 8:50 PM, Terry Nair wrote: Hi All, =20 Every end of the month, we clean up our entire membership database and = reset earn points, besides other parameters based on computational = norms. This is processed using WebDNA and we have been doing this = without issue for years. Once the lengthy process, initiated via a = browser url link is initiated, it may take anywhere from 8 to 10 minutes = before the "It is done" page is returned ....i.e. end of the process. =20 Well, our database have grown so large that now ....it is taking 15 = minutes to complete the process. WebDNA is not an issue because we can = see it happily doing its thing but ....the browser which is waiting for = the return page ....times out. I need to get the browser response page = back so as to know when to begin the next phase. Right now, when the = browser times out ....I remote into the server and check the Task = Manager which tells me when WebDNA has done its thing. Not elegant but = it works. =20 Breaking up the DB into smaller chunks to be processed separately is = one way to go ....however, was wondering if any of you guys can suggest = a better way of doing this ....getting the response I need when the job = is done. Being informed via SMS or email is not an option. =20 Thank for the assist folks. =20 Cheers Terry Nair =20 =20 --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us=20 --=20 Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com =20 Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 =20 Direct: 888.872.0274 Fax: 888.488.5924 =20 http://www.perosi.com --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us ------=_NextPart_000_055C_01D01295.8C72DF70 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

= Hi Matt,

=  

= The browsers I have used are IE8, IE10 and Chrome. The IE browser times = out first followed by Chrome which takes twice as long. Database size of = 70,000 records no issue =E2=80=A6.we are cleaning up 200,000+ = =E2=80=A6..it has grown and will continue to grow at a rate of 1000 = records a month.

=  

= I have done some research and it thought it was the =E2=80=9CConnection = Keep Alive=E2=80=9D settings, both on the browser and server, but no = such luck. Anyway =E2=80=A6.it looks like batching it up using smaller = sizes is probably the best way to go. Sigh =E2=80=A6..was hoping to get = lazy.

=  

= Cheers and thanks for the help =E2=80=A6.TDn

=  

From: Psi Prime Inc, Matthew A Perosi [mailto:matt@psiprime.com] =
Sent: Sunday, December 07, 2014 22:34
To: = talk@webdna.us
Subject: Re: [WebDNA] Circumnavigate Browser = Timeout On Lengthy WebDNA Operations

 

Terry,

What browser are you using?

For = many years I've been using the same steps to batch through up to 70,000 = records at a time.  Processing that many records takes a few hours = and my browser never timed out.  Although, I do find it easier to = batch through 9000 records at a time because the results page will = return in at most, 20 minutes.

I admit that I have not tried my = batch routine since upgrading to the latest version of Firefox and = Chrome.  I'm hoping your experience isn't related to a new browser = version.

If it's not related to a new browser version, then I = wonder if it's related to a setting on your computer or on the web = server.

Oh, another thought... I use Webmin all the time to = process my server backups.  Those never time out and they always = take more than 3 hours.

-Matt

On 12/6/2014 8:50 PM, Terry = Nair wrote:

Hi All,

 

Every = end of the month, we clean up our entire membership database and reset = earn points, besides other parameters based on computational norms. This = is processed using WebDNA and we have been doing this without issue for = years. Once the lengthy process, initiated via a browser url link is = initiated, it may take anywhere from 8 to 10 minutes before the "It = is done" page is returned ....i.e. end of the = process.

 

Well, our database have grown so large that now = ....it is taking 15 minutes to complete the process. WebDNA is not an = issue because we can see it happily doing its thing but ....the browser = which is waiting for the return page ....times out.  I need to get = the browser response page back so as to know when to begin the next = phase. Right now, when the browser times out ....I remote into the = server and check the Task Manager which tells me when WebDNA has done = its thing. Not elegant but it works.

 

Breaking up the DB into smaller chunks to be = processed separately  is one way to go ....however, was wondering = if any of you guys can suggest a better way of doing this ....getting = the response I need when the job is done. Being informed via SMS or = email is not an option.

 

Thank = for the assist folks.

 

Cheers = Terry Nair

 

=  

-------------------------------------------------------= -- This message is sent to you because you are subscribed to the mailing = list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/= list/talk@webdna.us Bug Reporting: support@webdna.us =




-- =
Matthew A Perosi
Corporate =Consultant
Mobile Marketing =Expert
Senior Web =Developer
SEO Analyst & =Educator
matt@psiprime.com
<= pre> 
Psi Prime, Inc.
323 =Union Blvd.
Totowa, NJ =07512
 
Direct:=C2=A0 =888.872.0274
Fax:=C2=A0=C2=A0=C2=A0=C2=A0 =888.488.5924
 
http://www.perosi.com
=

----------------------------------------------= ----------- This message is sent to you because you are subscribed to = the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/= list/talk@webdna.us Bug Reporting: support@webdna.us=

------=_NextPart_000_055C_01D01295.8C72DF70-- "Terry Nair"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

3.08 has trouble keeping the serial # ?? (2000) Re:Dumb Question about Docs (1997) notification solutions (1997) Rollovers (1999) Searching multiple Databases (1997) Pithy questions on webcommerce & siteedit (1997) Calculating Shipping (1997) Getting total number of items ordered (1997) Plugin or CGI or both (1997) Comments in db? (1997) nested context (1998) No more misunderstanding ... yay! :) (1997) [tcpsend] (2001) Automated FTP from Shell (2004) Help name our technology! (1997) [WebDNA] IIS 7.5 (2015) [Case] on OS X (2000) Re[2]: 2nd WebCatalog2 Feature Request (1996) os 8.5 (1999) [WebDNA] Sort Direction matches the written to file order (2015)