Well you can't just port the sheet as is. Would have to recreate the whole 'architecture' or enviroment that runs sheets.
Thats propriety Google, they dont share the code. So you can't just run a copy of the code. ... but it probably possibly to recreate whatever your sheet does as as dedicated app. Rather than been created in a 'sheet' would rewrite the application as a app in itself. For app engine would be a mix of a server side app in Python, Java, PHP or Go. And a client side component in html/javascript. Its entirely possible to make it 'fast' with that number of users. Sheets can't do it because its a generic application, used for all sorts of things (so there's lots of overhead for functions you not actually using). Whereas the new app would be tailor made for your functionality. But it would need a developer/coder to write this application. On 26 February 2016 at 21:06, Chris Lusk <chris.l...@dickasonlaw.com> wrote: > We currently use a Google Sheet from our Drive that has 9 tabs, about 30 > lines of script code, 50+ columns, 250+ rows, and has 13 to 20 people > accessing it at the same time every day. It is PAINFULLY SLOW! Would it > speed up if I could put this Sheet on the Compute engine or something....if > that's even possible? > > With more than 40 locations to serve you, please see www.dickasonlaw.com > for all of our signing locations. > > This email is intended only for the use of the party to which it is > addressed and may contain information that is privileged, confidential, or > protected by law. If you are not the intended recipient you are hereby > notified that any dissemination, copying or distribution of the email or > its contents is strictly prohibited. If you have received this message in > error, please notify us immediately, by replying to the message and > deleting it from your computer. > > > *Warning: *Internet communications are not assured to be secure or clear > of inaccuracies as information could be intercepted, corrupted, lost, > destroyed, arrive late or incomplete, or contain viruses. Therefore, we do > not accept responsibility for any errors or omissions that are present in > this email, or any attachment, that have arisen as a result of e-mail > transmission. > > Please send all closing package documents and links to > closingpacka...@dickasonlaw.com > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at https://groups.google.com/group/google-appengine. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/afa7ddea-0855-4612-b84c-0ba23a8aeefc%40googlegroups.com > <https://groups.google.com/d/msgid/google-appengine/afa7ddea-0855-4612-b84c-0ba23a8aeefc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAJCAUuK2N61i6qwxCkGz1rk93sMVoMu3UrLE1UCKA%3DM5aw4p6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
