Hi Group.
I'm trynig to create an application on google app engine website but
when I put my mobile phone say that i have en error.I try with Comcel
on Colombia. Thanks for any help.
Regards.
On 25 jul, 17:49, Jonathan Mayhak wrote:
> I think that I'm having the same problem.
>
> When I try
ort a sub 100ms
response.
In your case, your cellular modem may be responsible for a hefty
slice. It would be interesting if you could also plug into a decent
network and do the same test.
- Martyn
--~--~-~--~~~---~--~~
You received this message because you are subsc
Okay, just spoke with a network expert.
He suggests that Google are "any-casting" the DNS. So the pet-
software ping is not really doing a round-trip to the app-server.
Where "perhaps" the appspot.com ping is.
--~--~-~--~~~---~--~~
You received this message becau
I repeated Hawketts ping results for performance.latest.pet-
software.appspot.com and got similar times ~22ms.
So can anyone suggest why we experience such diverse request latency
if the underlying infrastructure is so good? - Hawkett (Australia)
reported avg 440ms with a ping of 22ms and I get 1
That's interesting!
On Aug 14, 9:41 am, hawkett wrote:
> Also from Orange, Australia -
>
> ping performance.latest.pet-software.appspot.com
> PING appspot.l.google.com (66.102.11.141): 56 data bytes
> 64 bytes from 66.102.11.141: icmp_seq=0 ttl=57 time=20.131 ms
> 64 bytes from 66.102.11.141: ic
Ouch!
On Aug 13, 8:58 pm, Jarek Zgoda wrote:
> Warsaw, Poland here. Typical ~240ms, ranging from 210ms to 740ms (!).
>
> On 13 Sie, 12:44, Martyn wrote:
>
>
>
> > Hi there,
>
> > I am investigating request latency for AppEngine after experiencing
> &g
I'll start off by reporting that:
In South-East England I am seeing typical latency reported at ~170ms,
but generally ranging between 160ms and 220ms
On Aug 13, 11:44 am, Martyn wrote:
> Hi there,
>
> I am investigating request latency for AppEngine after experiencing
> si
have created a simple version of an app I am working on,
that provides request timings. I would really appreciate it if people
could take a minute, try the link out and report back on the results.
Here is the link: http://performance.latest.pet-software.appspot.com
many thanks in advance
- Martyn
a bit.
- Martyn
On Aug 12, 7:26 pm, "Jeff S (Google)" wrote:
> Hi Martyn,
>
> The network topology between you and the App Engine server could also be a
> factor in this latency, so I might start by checking there. I'm also
> wondering how frequently you are mak
am using Java, so maybe this is not such a problem for python apps
and is related to routing to the JVM, I don't know.
Should I be able to plan for significantly reduced request latency in
the near future?
- Martyn
--~--~-~--~~~---~--~~
You received this messa
Thanks Nick, glad I wasn't going mad.
I have reported as issue 1962
- Martyn
On Aug 7, 4:28 pm, "Nick Johnson (Google)"
wrote:
> Hi Martyn,
>
> The Java interface to the Memcache API, unfortunately, is noticeably
> slower than the Python version. This is the
hope that helps
- Martyn
On 6 Aug, 16:44, Anna wrote:
> Hello,
>
> http://code.google.com/appengine/docs/java/datastore/overview.html
>
> After reviewing this document I am a little confused on how google
> stores data.
>
> In the example is the Employee object saved in
to the Java API perhaps?
If I batch three memcache puts using putAll, I see 13ms for the three
rather than 39ms.
On 30 July, 19:47, Martyn wrote:
> I am using the low-level Java Datastore interface and writing a
> "transactional" store - where each entity stores a number of dat
Do you know if it is possible to access the version string at runtime?
On 6 Aug, 13:42, Andi Albrecht wrote:
> On Thu, Aug 6, 2009 at 2:32 PM, Jason
>
> Salas wrote:
>
> > hi!
>
> > i was just wondering what the best practice should be for numbering my
> > app's versions in GAE. i just noticed
three times that.
On 6 Aug, 10:08, Martyn wrote:
> This is from a Google Code resource:
>
> "Memcache is a distributed RAM cache in which you can store transient
> data using a key-value model. Writes to memcache never touch the disk
> and are approximately 10 times faster in com
Yes Holger, I think that is right.
I am using the web.xml security-constraint declaration, which is
almost by definition implicit in the JVM deployment.
I confess to remaining confused over the precise method that the
UserService uses to access logged in user. My suspicion is that it may
use Mem
actually, using different yet similar versions should be an excellent
way to test multiple JVM interactions.
On 6 Aug, 10:26, Martyn wrote:
> ...should def work with VMWare though
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
...should def work with VMWare though
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, s
I thought so too but I'm pretty sure this didn't work when I tried
it before.
On 6 Aug, 10:11, Holger wrote:
> > > > But it does seem that it would be hard to have different logins in
> > > > different browser windows, which I would like for testing.
>
> I guess you could test simultanous di
This is from a Google Code resource:
"Memcache is a distributed RAM cache in which you can store transient
data using a key-value model. Writes to memcache never touch the disk
and are approximately 10 times faster in comparison to writes to the
datastore. Also, direct gets to memcache are approx
> Is the user logging out by clicking a 'logout' link you provided them
> (using the Users API), or by logging out on some other Google service?
> If the latter, it's quite possible that doing so would not log the
> user out of all their App Engine apps immediately, yes. If you want a
> user to b
Actually I guess I can achieve that by using two different app
versions ;-)
On 5 Aug, 18:29, "Nick Johnson (Google)"
wrote:
> On Wed, Aug 5, 2009 at 6:24 PM, Martyn wrote:
>
> > Yes, I was assuming that if the user (in the browser) signed into
> > another account
uot; +
timer.elapsed() + "");
I get ~1380ms for each of the tests, so approx 14ms for each api call.
Any suggestions?
- Martyn
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine&quo
s for your feedback today!
- Martyn
On 5 Aug, 16:12, Holger wrote:
> Hi Martyn,
>
> if you just started maybe you should consider to change to Python.
>
> Java might be more common outside the appengine world - but within
> appengine there exist far better ready made soluti
n app sign-out link.
But it does seem that it would be hard to have different logins in
different browser windows, which I would like for testing.
On 5 Aug, 17:09, "Nick Johnson (Google)"
wrote:
> On Wed, Aug 5, 2009 at 3:21 PM, Martyn wrote:
>
> > I'm sorry, I am clearly
ow RTFL on user authentication and see what I can learn.
Sorry if I've been wasting your time.
- Martyn
On Aug 5, 2:52 pm, "Nick Johnson (Google)"
wrote:
> On Wed, Aug 5, 2009 at 2:20 PM, Martyn wrote:
>
> > Are you suggesting that I need to do something in my App fo
Are you suggesting that I need to do something in my App for each
request to ensure the current user returned is valid?
I have no control if the user changes their account sign-in in another
browser window.
My debug code is
UserService us = UserServiceFactory.getUserService();
Since I sign in as a different user, this cannot be explained by a
cookie problem.. plus the timing issue.
On Aug 5, 1:12 pm, Holger wrote:
> If logout wouldn't work, that would be really important - sure.
>
> But it needn't to be appengine creating this result, it can be your
> own code too.
>
seems to
have made no significant difference. I did test "pre-puts", batching
say one-hundred inserts, and then seeing if update of an existing
entity was any better - it wasn't.
I will get back with some more metrics in a bit.
On Aug 5, 1:14 pm, "Nick Johnson (Google)&
I think this is an important issue - why no response?
On Aug 5, 9:48 am, Martyn wrote:
> Hi there,
>
> In testing I have noted latency in user identity management when I
> sign in and out as different account users.
>
> 1) I sign in as user A - application recognises me as
eries, Blob of
around 1k).
- Martyn
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group
ew minutes not hours/days.
Could the post have been lost?
cheers
- Martyn
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@g
I am using the low-level Java Datastore interface and writing a
"transactional" store - where each entity stores a number of data
updates in a single Blob.
Each transaction requires two updates, one to a Header entity, and one
to the new transaction data entity. Keys for each are created
explicit
33 matches
Mail list logo