I’ve joined insync in February of 2013, since there I have experienced the slowness problem and checked over the years that many people has the same problem and opened tickets in here.
Could you please explain what is going on? Is it a google API connections limits or something serious happening?
Because I can’t seriously accept other reason than that.
I would love to use InSync again and even pay it one more time, but you MUST change this.
Thank you and really expect some transparency about this issue.
@renatomefidf One of the motivations for limiting the number of connections is the issues we receive from users that makes their network congested (and unusable) when we had a higher number of simultaneous connections. Ideally, we should be able to automatically adjust that and it’s on our list. As a quick workaround, we’re planning to have an advanced configuration option where you can set the maximum number of simultaneous connections.
Thanks for clarifying the issue, its a really important thing for those coming from dropbox or which has too many files.
How long can I expected to have this advanced configuration? I could even work with a config file and would be happy with it!
I am really interested on that feature as well, I use insync on dedicated servers and I have lots of small files, this is a real problem for us, it will be taking days to do an initial sync.
At this point I think it’s just a joke
It’s being more than 5 years and it is that hard to make a field with the number of connections… (I’d understand if it’s a google api limit, but doesn’t look like the case from what Marte said)
Google doesn’t have a hard limit on parallel connections, but will punish you if API calls are too frequent. Some Insync users actually encountered this problem last year or so, when Insync only had 2 connections. Now it’s already increased to 4, on par with most other clients.
In this case what’s the relationship between amount of files and simultaneous calls, is the API allowing “bursts”? If I only have a couple of hundred files and 10 connections, am I going to be “punished”?
I think it’s a topic which deserves study rather than guessing, since the UX can be dramatically improved.
The official hard line is 1000 queries per 100 seconds per user. There’re also global limits on the client id (i.e. all Insync users / installations combined), whose usage situation is only known to Insync, and difficult for us users to gauge.
In the simplest use case, a file upload can take just one API call. But to provide more sophisticated features in Insync, a few more calls may be needed (I don’t know, only guessing).
I’m pretty sure Insync has experimented with ways to increase transfer speed and limits of API calls. Every serious developer who writes software for Google services would do so. It’d be crazy not to.
The fact that they stayed with only 2 parallel connections for so long, despite numerous requests and complaints, should be a very clear sign that the problem is not simple.
