Re: response for server every second

From	Jerry Stuckle <jstucklex@attglobal.net>
Newsgroups	comp.lang.php
Subject	Re: response for server every second
Date	2015-06-10 13:23 -0400
Organization	A noiseless patient Spider
Message-ID	<ml9rom$g5j$1@dont-email.me> (permalink)
References	<94be00e7-99d7-4d84-97a5-538535a0317d@googlegroups.com> <55784c9c$0$2956$e4fe514c@news2.news.xs4all.nl> <ml9mkb$phu$1@dont-email.me> <slrnmngqmk.14s6.knock_yourself_out@vps.jonz.net>

Show all headers | View raw

On 6/10/2015 12:50 PM, Allodoxaphobia wrote:
> On Wed, 10 Jun 2015 11:55:51 -0400, Jerry Stuckle wrote:
>> On 6/10/2015 10:41 AM, Erwin Moller wrote:
>>> On 6/10/2015 3:59 PM, apoorv.kanungo@gmail.com wrote:
>>>> I want to get response from server every one second, the output will
>>>> contain some value which I need to process in front end.
>>>>
>>>> In backend I am using some queries to read data from mysql and return
>>>> me output.
>>>>
>>>> Things I have tried 1) Ajax 2) Webserver Events 3) Amazon Cloudfront
>>>>
>>>> None of these work for me usually it is taking 3-4 seconds to get me
>>>> response,
>>>>
>>>> classic example to see this working(getting output in one sec)
>>>>
>>>> http://madbid.com
>>>>
>>>> Please let me know if anyone has some solution for this.
>>>
>>> Hi,
>>>
>>> I have 2 observations:
>>>
>>> 1) How many clients are requesting that info on the server?
>>> If you have multiple clients, think over your design (i'll come back to
>>> that)
>>> Let's look at XML HTTP Request (XHR) first (what you called AJAX):
>>> What happens?
>>> a) Client request a PHP page
>>> b) Server much launch the process
>>> c) PHP runs, and starts a database query
>>> d) Database processes the query, and answers
>>> e) PHP delivers the answer as output back to the requesting client
>>> f) Client updates the screen
>>>
>>> This is just not feasible every second.
>>> Try that with 1000 clients. ;-)
>>> There is so much overhead involved, and networking, you can't expect
>>> this to run every second.
>>>
>>> Solution:
>>> Create a cronjob that runs every second.
>>> Let it call your PHP script that queries the database.
>>> Instead of responding to a client, let PHP put its output in a file in a
>>> public directory.
>>> Let XHR directly fetch this file.
>>> This is much faster.
>>>
>>> Warning: write the file as myOutput_tmp.xml, then rename to
>>> myOutput.xml, otherwise you risk trying to read a file that is in the
>>> process of being written.
>>> I assume that your PHP script end within the second, otherwise you have
>>> another problem. If, for example, your DB query takes 5 secs, the whole
>>> adventure will fail, whatever you try.
>>>
>>> Did you take timestamps for the whole PHP script (from start to end)?
>>> If that is close to 1 second, you have to find another solutionr
>>
>> While yours are all good suggestions, it's still no guarantee, Erwin.
>> Even just retrieving a static page can take more than 1 second,
>> depending on server load, available bandwidth, client load and even
>> which browser is to parsing the HTML.
>>
>>> 2) Use nodeJS
>>> Indeed, no PHP. No AJAX.
>>> NodeJS is extremely fast and supports sockets.
>>> If you are a bit familiar with ECMA Script (such as Javascript), try
>>> this route.
>>
>> Another possibility.  So is a Java applet, .NET and probably a dozen
>> other ways, all of which he can find better help on an appropriate
>> newsgroup.
> 
> 
> Of course, if this is all wholly on a _local_ network....
>

The same applies to a local network.  They can have slow response time,
also.

> 
> sigh...  
> The Internet Of Things is really going to raise the noise floor 
> on the interweb.....
> 

What is the "interweb"?  There's the world wide web, and internet.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

Thread

response for server every second apoorv.kanungo@gmail.com - 2015-06-10 06:59 -0700
  Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-10 10:18 -0400
  Re: response for server every second Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-06-10 16:41 +0200
    Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-10 11:55 -0400
      Re: response for server every second Allodoxaphobia <knock_yourself_out@example.net> - 2015-06-10 16:50 +0000
        Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-10 13:23 -0400
          Re: response for server every second Richard Yates <richard@yatesguitar.com> - 2015-06-10 10:37 -0700
            Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-10 14:27 -0400
    Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-10 23:38 -0700
    Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-11 00:14 -0700
      Re: response for server every second Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-06-11 12:09 +0200
        Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-11 04:16 -0700
          Re: response for server every second Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-06-11 14:37 +0200
            Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-11 06:20 -0700
              Re: response for server every second Matthew Carter <m@ahungry.com> - 2015-06-11 13:45 -0400
            Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-11 23:35 -0700
              Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-12 09:10 -0400
          Re: response for server every second Denis McMahon <denismfmcmahon@gmail.com> - 2015-06-12 03:59 +0000
            [off topic nodejs advertisement] Was Re: response for server every second Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-06-15 16:08 +0200
              Performance of PHP vs. Node.js (was: [off topic nodejs advertisement]) "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-06-15 20:42 +0200
                Re: Performance of PHP vs. Node.js Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-06-16 00:20 +0200
                Re: Performance of PHP vs. Node.js "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-06-16 00:58 +0200
          Re: response for server every second gordonb.890nt@burditt.org (Gordon Burditt) - 2015-06-13 13:39 -0500
            Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-18 23:16 -0700
              Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-19 08:16 -0400
                Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-21 23:06 -0700
                Re: response for server every second "Peter H. Coffin" <hellsop@ninehells.com> - 2015-06-22 08:03 -0500
                Re: response for server every second Denis McMahon <denismfmcmahon@gmail.com> - 2015-06-23 06:39 +0000
                Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-23 07:23 -0400
    Re: response for server every second Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-22 18:37 +0200
      Re: response for server every second Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-22 18:42 +0200
      Re: response for server every second Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-06-23 17:11 +0200
        Re: response for server every second Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-24 00:06 +0200
          Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-23 19:10 -0400
            Re: response for server every second Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-24 01:45 +0200
              Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-23 20:21 -0400
                Re: response for server every second apoorv.kanungo@gmail.com - 2015-06-23 23:34 -0700
                Re: response for server every second bill <william@TechServSys.com> - 2015-06-24 06:58 -0400
                Re: response for server every second Arno Welzel <usenet@arnowelzel.de> - 2015-06-25 17:18 +0200
                Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-25 20:31 -0400
                Technical requiremenets for Usenet messages (was: Re: response for server every second) Arno Welzel <usenet@arnowelzel.de> - 2015-06-26 10:43 +0200
                Re: Technical requiremenets for Usenet messages Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-26 21:47 +0200
                Re: Technical requiremenets for Usenet messages Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-26 22:19 +0200
                Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-25 23:07 -0400
                Re: response for server every second Arno Welzel <usenet@arnowelzel.de> - 2015-06-26 10:21 +0200
                Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-26 06:48 -0400
                Technical requirements for Usenet messages (was Re: response for server every second) Arno Welzel <usenet@arnowelzel.de> - 2015-06-26 13:48 +0200
                Re: Technical requirements for Usenet messages (was Re: response for server every second) Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-26 14:29 -0400
                Re: Technical requirements for Usenet messages Arno Welzel <usenet@arnowelzel.de> - 2015-06-27 14:49 +0200
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-27 10:25 -0400
                Re: Technical requirements for Usenet messages Arno Welzel <usenet@arnowelzel.de> - 2015-06-28 17:52 +0200
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-28 20:08 -0400
                Re: Technical requirements for Usenet messages "Peter H. Coffin" <hellsop@ninehells.com> - 2015-06-27 22:14 -0500
                Re: Technical requirements for Usenet messages Arno Welzel <usenet@arnowelzel.de> - 2015-06-28 17:54 +0200
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-28 20:10 -0400
                Re: Technical requirements for Usenet messages Arno Welzel <usenet@arnowelzel.de> - 2015-06-30 09:54 +0200
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-30 08:45 -0400
                Re: Technical requirements for Usenet messages Arno Welzel <usenet@arnowelzel.de> - 2015-06-30 16:20 +0200
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-30 15:00 -0400
                Re: Technical requirements for Usenet messages Arno Welzel <usenet@arnowelzel.de> - 2015-07-06 13:36 +0200
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-07-06 11:56 -0400
                Re: Technical requirements for Usenet messages Richard Heathfield <rjh@cpax.org.uk> - 2015-07-06 18:54 +0100
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-07-06 16:54 -0400
                Re: Technical requirements for Usenet messages Richard Heathfield <rjh@cpax.org.uk> - 2015-07-07 00:00 +0100
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-07-06 22:08 -0400
                Re: Technical requirements for Usenet messages Richard Heathfield <rjh@cpax.org.uk> - 2015-07-07 07:24 +0100
                Re: Technical requirements for Usenet messages Jerry Stuckle <jstucklex@attglobal.net> - 2015-07-07 10:41 -0400
                Re: Technical requirements for Usenet messages apoorv.kanungo@gmail.com - 2015-07-09 22:52 -0700
                Re: Technical requirements for Usenet messages Denis McMahon <denismfmcmahon@gmail.com> - 2015-07-02 03:07 +0000
                Re: response for server every second Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-26 21:13 +0200
            Re: response for server every second Richard Heathfield <rjh@cpax.org.uk> - 2015-06-24 09:52 +0100
              Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-24 09:21 -0400
                Re: response for server every second Richard Heathfield <rjh@cpax.org.uk> - 2015-06-24 18:48 +0100
                Re: response for server every second Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-06-24 20:55 +0200
                Re: response for server every second Richard Heathfield <rjh@cpax.org.uk> - 2015-06-24 20:55 +0100
                Re: response for server every second Jerry Stuckle <jstucklex@attglobal.net> - 2015-06-24 15:21 -0400
                Re: response for server every second Richard Heathfield <rjh@cpax.org.uk> - 2015-06-24 20:35 +0100

csiph-web