Reputation
290
Top tag
Next privilege 300 Rep.
Create new tags
Badges
1 3 13
Newest
 Curious
Impact
~16k people reached

  • 0 posts edited
  • 2 helpful flags
  • 11 votes cast
1d
comment Can fast, optimized server calls collapse a server?
@9000 hmmm, well, both are important! But of course, life is full of decisions. To me, after looking at the numbers, it simply looks like the MySQL server was having a bad time, but I can't contrast it with numbers. In some cases, it looked like there were too many accesses from one single script, and after another one wanted to do the same, the DB was locked and it had to wait for too much, stacking requests, and collapsing the server. We reduced the latency (I'm taking your word!), but something that was magically balanced before (too much time for PHP and DB) was now out of control.
2d
comment Can fast, optimized server calls collapse a server?
@9000 Sadly the tools we had were pretty limited (we couldn't install monitoring systems). We could only track the average time a request takes to be processed, the amount of memory used by PHP and the overall server load
2d
accepted Can fast, optimized server calls collapse a server?
2d
comment Can fast, optimized server calls collapse a server?
@cdkMoose Indeed, the server requests were taking a lot because we were doing pretty heavy queries and all of them started stacking on top of others. We tried to do the process the other way around (first optimizing the MySQL, testing it and then improving the php parts) and everything started going smoothly. If you add this as an answer, I can just accept it!
Jul
24
comment Is modifying the User Agent potentially dangerous?
It took quite a while to reimplement all the api calls, but we ended leaving the UA as it was, and stuffing any needed info as other parameters. Thanks @cxw!
Jul
24
accepted Is modifying the User Agent potentially dangerous?
Jul
24
awarded  Curious
Jul
23
asked Can fast, optimized server calls collapse a server?
Jul
15
comment Is modifying the User Agent potentially dangerous?
@cxw native code stands by code in the platform specific language (Java for Android, Objective-C or Swift for iOS). Hybrid means javascript, in my case. The change is done on the application creation. I already have alternate calls to define the best protocol to make calls. That works, so that's why I thought it could be download related
Jul
15
asked Is modifying the User Agent potentially dangerous?
Jul
10
awarded  Citizen Patrol
Mar
2
revised Mobile App Development-Architecture/Platform: Main performance concern: device/UI responsiveness
added 1 character in body
Feb
24
awarded  Popular Question
Sep
1
awarded  Teacher
Sep
1
answered Mobile App Development-Architecture/Platform: Main performance concern: device/UI responsiveness
May
9
awarded  Famous Question
Mar
26
accepted Are web application usability issues equal to website usability issues?
Mar
26
accepted What are the pros and cons of Node.js?
Apr
17
comment Should website frontends be rendered in client-side or server-side?
It should work in IE8, as mentioned to @LucFranken, so History is not available yet. Plus the site is amazingly small, and Wordpress is too big, even for this case. But thanks for your comment
Apr
16
comment Should website frontends be rendered in client-side or server-side?
Hehe, I partially disagree with your last statement, but because I know the limitations of the project [it should run on IE8, thus history isn't available yet. We went across this thing too =( ], so I was playing with an advantatge. Apart from that, I agree with every point. And that's right, the specifications dictate the path to follow. Finally, we moved to an intermediate solution, with friendly urls from PHP and presentation+localisation from JavaScript. I'd personally have pushed localisation to PHP and presentation to HTML, leaving the behaviors to JavaScript.