Slow performance recently?

223 views
Skip to first unread message

m...@maxtannone.com

unread,
Aug 8, 2016, 12:47:27 PM8/8/16
to back{4}app
Has anyone else's app slowed considerably over the past day or two? I've noticed a huge decrease in performance. I'm still in beta testing, so it's not like I have an increase in number of users...

m...@maxtannone.com

unread,
Aug 8, 2016, 12:55:18 PM8/8/16
to back{4}app
I also noticed this in the output of the logs..

Cloud Code not loaded:
 { [Error: Cannot find module './data/cloud/main'] code: 'MODULE_NOT_FOUND' }
 [33mwarn [39m: Unable to ensure uniqueness for usernames:  Error: getaddrinfo ENOTFOUND mongodb2.back4app.com mongodb2.back4app.com:27017
    at errnoException (dns.js:26:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)
 [33mwarn [39m: Unabled to ensure uniqueness for user email addresses:  Error: getaddrinfo ENOTFOUND mongodb2.back4app.com mongodb2.back4app.com:27017
    at errnoException (dns.js:26:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)

smac...@gmail.com

unread,
Aug 8, 2016, 2:47:58 PM8/8/16
to back{4}app
Yes, they are aware of the issues.  The problems started about 8am EST and things are still moving like molasses on a cold winter's day.

Ricardo Seiji

unread,
Aug 8, 2016, 3:33:49 PM8/8/16
to back{4}app
Hey there, guys.

We're sorry about the issues we're facing today.

Things got slow and we're working hard to get things back to normal again.
The logs were caused by timeouts on mongodb connections.

We'll solve those problems and things will move like the waters of the Bruinen River, next to Rivendell. (Without the horses, we don't have Gandalf here)

Regards,
Ricardo Seiji.

Davi Macêdo

unread,
Aug 8, 2016, 5:44:22 PM8/8/16
to back{4}app
Hi, Guys. Everything working fine again. If you still have any problem, let me know.
Message has been deleted

jo...@talkingcucumber.com

unread,
Aug 9, 2016, 1:00:44 PM8/9/16
to back{4}app
I'm seeing another slow-down today. Is this just me...?

Davi Macêdo

unread,
Aug 9, 2016, 1:05:43 PM8/9/16
to back{4}app
Hi, Joel.

Servers are running smoothly and any other user haven't reported any performance issue.

I am monitoring server response all day long since yesterday and it is pretty fast and normal since yesterday.

Could you please send me your app id so I can check your logs?

Best!

avko...@gmail.com

unread,
Aug 10, 2016, 6:46:53 AM8/10/16
to back{4}app
I'm having performance issues during the last 5-6 ours.
AppID: fguirJlzbYOm7EjFBlChhaieFIHUkRUEwP24hSjk

smac...@gmail.com

unread,
Aug 10, 2016, 7:00:26 AM8/10/16
to back{4}app
Down again for me.

ios...@gmail.com

unread,
Aug 10, 2016, 7:04:39 AM8/10/16
to back{4}app
Same here.  I've had numerous cases of the server just not responding or being slow since Aug 7.  I'm in the final stage of testing and this is becoming a major problem.

ios...@gmail.com

unread,
Aug 10, 2016, 7:06:32 AM8/10/16
to back{4}app
App id: A1E9fvKcZqWeyuEEg7UoP3KoVtu3yLGnE9zryrPW

avko...@gmail.com

unread,
Aug 10, 2016, 7:06:34 AM8/10/16
to back{4}app
Yeah, it's already countless times today I see these 3 coloured circles running in circles when trying to get into the Dashboard...

smac...@gmail.com

unread,
Aug 10, 2016, 7:08:42 AM8/10/16
to back{4}app
Indeed, a MAJOR problem for me.  Just shoot me now.

avko...@gmail.com

unread,
Aug 10, 2016, 7:09:21 AM8/10/16
to back{4}app
I'm already thinking about moving my test data to parse.com. It won't be easy because of the files stored in the database - but...

ios...@gmail.com

unread,
Aug 10, 2016, 7:09:47 AM8/10/16
to back{4}app

ERROR[;: [fg243,36,73;Optional(Error Domain=Parse Code=100 "The request timed out." UserInfo={code=100, NSLocalizedDescription=The request timed out., originalError=Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSUnderlyingError=0x7fa977d29670 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=https://parseapi.back4app.com/classes/Spot, NSErrorFailingURLKey=https://parseapi.back4app.com/classes/Spot, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.}, temporary=1, error=The request timed out., NSUnderlyingError=0x7fa974785570 {Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSUnderlyingError=0x7fa977d29670 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=https://parseapi.back4app.com/classes/Spot, NSErrorFailingURLKey=https://parseapi.back4app.com/classes/Spot, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.}}})[;


smac...@gmail.com

unread,
Aug 10, 2016, 7:10:41 AM8/10/16
to back{4}app
Everything started out so well here.   Is there any other service offering a parse server replacement?  

ios...@gmail.com

unread,
Aug 10, 2016, 8:30:13 AM8/10/16
to back{4}app
I'm thinking of going back to Parse.com.  I'm beta testing an iOS app, and that will buy me some time to find a reliable replacement.  The last thing I need now is a flaky Parse backend.

Olivier Douangvichith

unread,
Aug 10, 2016, 8:36:37 AM8/10/16
to back{4}app
I think you can't go back to Parse.com once your migration has finished!

Gabriel Lemos

unread,
Aug 10, 2016, 4:22:39 PM8/10/16
to back{4}app
Hi Community,

At first, we do appologize the recent instability on some Apps at back4app. We faced some problems due to a huge increase of migrating Apps a few days ago. Due to a Parse deadline many apps migrated recently to back4app and we face some problems migrating a huge volume of Apps at the same time.

For now we have replicated our Parse Server structure in many servers and the sevice is stable. We have already identified the root causes and we are working on the solution. We are working on the Parse Server architecture and hope to finish this by the end of this week.

Back4app is now a family with more than 7k apps. Our community is growing very fast and our team is continuously working together with the Open Source community and the Parse.com Team to provide you a consistent and complete backend platform.
We are very proud of your confidence and assure you that we always going to do our best.
Reply all
Reply to author
Forward
0 new messages