Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #15474
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: response for server every second |
| Date | 2015-06-19 08:16 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <mm113q$ppt$1@dont-email.me> (permalink) |
| References | (2 earlier) <265d8474-cafc-4ca2-9f87-3d3502f92a29@googlegroups.com> <55795e6b$0$2931$e4fe514c@news2.news.xs4all.nl> <6f1bbfe0-6d62-4f2b-bcc1-1131aaf8b50f@googlegroups.com> <7JKdnQxmpetZ5eHInZ2dnUU7-XOdnZ2d@posted.internetamerica> <bbba1ed9-c97e-4d0f-a30b-718604f0973b@googlegroups.com> |
On 6/19/2015 2:16 AM, apoorv.kanungo@gmail.com wrote: > On Sunday, June 14, 2015 at 12:09:07 AM UTC+5:30, Gordon Burditt wrote: >>> It's more like a bidding platform when a user bid on a item that >> value is stored in database when he bids again that value is updated >> or new value is inserted in database with the same id and so on. >> >>> now imagine thousands of user logging in and bidding and there >> is a sort of timer that updates itself every time a user bids. The >> person who bid last when the timer expires will be declared winner >> of the bid. >> >> Is it practical to use a dedicated bid-server program rather than >> a web server? The bid-server is hard-coded (if necessary, in >> hand-optimized assembly language) to process exactly *ONE* query >> URL, (maybe with some variable inputs) and gives out a 500 error >> for anything else. (The rest of the site you put on a different >> web server.) The program accesses no static files; these are hard-coded >> into the executable. It's unclear whether this program needs a >> database, or it can *BE* a database, keeping track of at least the >> current high bids in shared memory. >> >> Is it necessary for the bid-server to wait for the client to ask >> for a response, or is it acceptable to just continue generating >> responses one a second until the connection breaks? >> >> >> I am reminded here of the little SMTP "server" I put up once that >> accepted a connection, forked, read a line of input, output "550 >> Spam Not Welcome Here", and went back to read another line. On >> EOF, close the socket and the child exits. It managed to throw >> away hundreds of mail messages a second (on one SMTP connection - >> some spammers have been caught sending over a million SPAMs in one >> SMTP connection, all of them rejected). >> >> This machine wasn't supposed to need mail at all, and we knew of >> no MX records pointing at it, it attracted a lot of incoming mail >> connections. It was supposed to be a minimum-configuration machine >> for testing applications to be sure they were acceptably fast. It >> turned out that some of the GUI-ish apps needed more memory to >> outrun a snail. > > Very good suggestion Gordon but I am struggling that how would I do such when I have to store value in the database and also retrieve them. > > I am thinking that I would maintain a text file and store all values on them with fwrite and them at some point run a cron that will store them in the database. > > another option I am thinking is json but all that encoding,decoding and parsing will affect the performance. > Why take an extra step of storing the data in a file? It's just more complication and overhead. It will take the same amount of time to store the data in the database, no matter how you do it. -- ================== Remove the "x" from my email address Jerry Stuckle jstucklex@attglobal.net ==================
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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