[google-appengine] Channel API on SSL

[cloudpre]

Hi - does GAE allow channel api over SSL?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/ezxXyQsI3xkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] more than 12M operations in less than 10 hrs

[cloudpre]

Hi - my app is taking more than 12M reads in less than 10 hours- is
there a tuner to check which calls are exhibiting this weird behavior?

I mean how do we tune this?

Thanks.

-- 
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, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Datastore Small Operations - datastore.get(key)

[cloudpre]

Hi

We have a pretty big app which has not been optimized till date. We
spend over $40/day just on the reads.

This is our current stats

Datastore Read Operations46.74 Million Ops   46.69   $0.70/ 
Million
Ops  $32.69
Datastore Small Operations   0.00 Million Ops0.00$0.10/ 
Million
Ops  $0.00


I have been reading that small operations are much cheaper and they
are done based on key.

The following function is used at many places - but I do not see
counter moving from zero for small operations.

Is datastore.get(key) a small operation? If not, what should I change
the function to make it count towards small operations.

Thanks.

// Get Entity
public static Entity getEntityFromId(String entityName, String id)
{
// Get Datastore
DatastoreService datastore =
DatastoreServiceFactory.getDatastoreService();

// Get Entity
try
{
Key key = KeyFactory.stringToKey(id);
return datastore.get(key);
} catch (Exception e)
{
return null;
}
}

-- 
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, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Datastore Small Operations - datastore.get(key)

[cloudpre]

Jeff - thanks for the note. I have been trying to add few items in
memcache manually.

Can put operations also be saved? Let's say I am updating the same
query again after few seconds.

Does it work flawlessly in the production? The last thing I want to
see is our thousands of customers coming back and complaining.

Cheers.

On Apr 18, 12:17 am, Jeff Schnitzer  wrote:
> Get-by-key is a read operation, not a small operation.  Small
> operations are things like count() index walks and keys-only queries
> (although there is still 1 read operation per query).
>
> Most read-heavy apps can benefit significantly from memcache.  If
> you're using the low-level api, try this:
>
> http://code.google.com/p/objectify-appengine/wiki/MemcacheStandalone
>
> Jeff
>
>
>
> On Wed, Apr 18, 2012 at 2:27 AM, cloudpre  wrote:
> > Hi
>
> > We have a pretty big app which has not been optimized till date. We
> > spend over $40/day just on the reads.
>
> > This is our current stats
>
> > Datastore Read Operations                46.74 Million Ops       46.69   
> > $0.70/ Million
> > Ops      $32.69
> > Datastore Small Operations               0.00 Million Ops        0.00    
> > $0.10/ Million
> > Ops      $0.00
>
> > I have been reading that small operations are much cheaper and they
> > are done based on key.
>
> > The following function is used at many places - but I do not see
> > counter moving from zero for small operations.
>
> > Is datastore.get(key) a small operation? If not, what should I change
> > the function to make it count towards small operations.
>
> > Thanks.
>
> > // Get Entity
> >        public static Entity getEntityFromId(String entityName, String id)
> >        {
> >                // Get Datastore
> >                DatastoreService datastore =
> > DatastoreServiceFactory.getDatastoreService();
>
> >                // Get Entity
> >                try
> >                {
> >                        Key key = KeyFactory.stringToKey(id);
> >                        return datastore.get(key);
> >                } catch (Exception e)
> >                {
> >                        return null;
> >                }
> >        }
>
> > --
> > 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, send email to 
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/google-appengine?hl=en.

-- 
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, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Datastore Small Operations - datastore.get(key)

[cloudpre]

Thanks Robert.

Jeff - thanks for chipping in.

I wanted to check if puts are also cached - eg: entity with same
values being written over and over again - will they be actually be
written to datastore.

I will use 3.1 - I liked the Global cache very much.

Twig kept the syntax simpler but I do not like the lack of caching
which will affect the high-volume apps.




On Apr 18, 9:49 am, Jeff Schnitzer  wrote:
> On Wed, Apr 18, 2012 at 3:36 AM, cloudpre  wrote:
> > Jeff - thanks for the note. I have been trying to add few items in
> > memcache manually.
>
> > Can put operations also be saved? Let's say I am updating the same
> > query again after few seconds.
>
> I'm not sure what you mean here.  The cache covers get(), put(), and
> delete() operations.  Queries do not affect the cache at all.
> However, you can convert queries into keys-only queries followed by
> batch get()s; this will cost small datastore operations for cache hits
> rather than full read operations.  Objectify4 will actually do this
> for you.
>
> > Does it work flawlessly in the production? The last thing I want to
> > see is our thousands of customers coming back and complaining.
>
> There have not been any complaints for the current cache code (3.1+),
> and it is fairly widely used.  Older versions of the cache code (3.0
> and prior) had synchronization issues, but for 3.1 I rewrote it with
> some help from Ari and Alfred (Google).  It should be transactionally
> safe - even under heavy contention - as long as you don't hit
> DeadlineExceededExceptions.
>
> Jeff

-- 
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, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Datastore Small Operations - datastore.get(key)

[cloudpre]

Thanks. I will use CachingDatastoreService - As a suggestion, you
should put a list of customers using it so that they know that it's
proven.

On Apr 18, 12:22 pm, Jeff Schnitzer  wrote:
> On Wed, Apr 18, 2012 at 2:45 PM, cloudpre  wrote:
> > Thanks Robert.
>
> > Jeff - thanks for chipping in.
>
> > I wanted to check if puts are also cached - eg: entity with same
> > values being written over and over again - will they be actually be
> > written to datastore.
>
> The cache is write-through; all put()s go straight to the datastore
> and then expire the cache content.  The cache is refreshed on a
> subsequent get().
>
> > I will use 3.1 - I liked the Global cache very much.
>
> > Twig kept the syntax simpler but I do not like the lack of caching
> > which will affect the high-volume apps.
>
> If you're just using the low-level api, the CachingDatstoreService in
> the Objectify 3.1 jar is the same as what's in trunk (Objectify4).  If
> you're actually thinking of using Objectify, grab trunk - Objectify4
> has a more Twig-ish syntax and has folded in many of Twig's features
> (with John Patterson's design help).
>
> Jeff

-- 
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, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Datastore Small Operations - datastore.get(key)

[cloudpre]

I settled with Generic DAO classes for Objectify wrapped by Jersey.

I am using Backbone for the frontend MVC - so far, I have to admit
that it is shaping up well.

Jerff - thanks for the library.

On Apr 20, 8:48 am, Jeff Schnitzer  wrote:
> No, get-by-key that reaches the datastore is a Read Operation.
> However, memcache hits are free.
>
> Jeff
>
>
>
> On Fri, Apr 20, 2012 at 1:56 AM, Peter Han  wrote:
> > "However, you can convert queries into keys-only queries followed by
> > batch get()s; this will cost small datastore operations for cache
> > hits
> > rather than full read operations"
>
> > keys-only query is a small datastore operation thats is clear, but
> > batch get of entities by key also? Thank you.
>
> > On Apr 18, 6:49 pm, Jeff Schnitzer  wrote:
> >> On Wed, Apr 18, 2012 at 3:36 AM, cloudpre  wrote:
> >> > Jeff - thanks for the note. I have been trying to add few items in
> >> > memcache manually.
>
> >> > Can put operations also be saved? Let's say I am updating the same
> >> > query again after few seconds.
>
> >> I'm not sure what you mean here.  The cache covers get(), put(), and
> >> delete() operations.  Queries do not affect the cache at all.
> >> However, you can convert queries into keys-only queries followed by
> >> batch get()s; this will cost small datastore operations for cache hits
> >> rather than full read operations.  Objectify4 will actually do this
> >> for you.
>
> >> > Does it work flawlessly in the production? The last thing I want to
> >> > see is our thousands of customers coming back and complaining.
>
> >> There have not been any complaints for the current cache code (3.1+),
> >> and it is fairly widely used.  Older versions of the cache code (3.0
> >> and prior) had synchronization issues, but for 3.1 I rewrote it with
> >> some help from Ari and Alfred (Google).  It should be transactionally
> >> safe - even under heavy contention - as long as you don't hit
> >> DeadlineExceededExceptions.
>
> >> Jeff
>
> > --
> > 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, send email to 
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/google-appengine?hl=en.

-- 
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, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Reducing instance startup time JSP taglib scanning

[cloudpre]

I have exactly the same issue. For me, it takes more than 21secs for it to 
scan just this one. The system is not slow.




Aug 1, 2012 *1:58:47 AM *com.google.apphosting.utils.jetty.JettyLogger debug

FINE: TLD search of 
file:/x/eclipse/plugins/com.google.appengine.eclipse.sdkbundle_1.6.4.v201203300216r36/appengine-java-sdk-1.6.4/lib/tools/jsp/repackaged-appengine-jasper-jdt-6.0.29.jar

Aug 1, 2012 *1:59:08 AM* com.google.apphosting.utils.jetty.JettyLogger debug

FINE: Init SecureRandom.

---

Is there a way to disable taglib totally so that it does not scan? The 
entire application has been built for speed and this thing discourages me.

Thanks.

On Tuesday, July 10, 2012 6:07:14 AM UTC-7, Jordi P.S. wrote:
>
> Trying to reduce the startup time of my instances I've come accross the 
> taglib classpath scanning.
>
> My application has 50mb of jars. According to a yourkit profiling session: 
> the scanning of the tld takes 20% of the startup time.
>
> Is there a way to disable that? I just use JSTL standard libs which are 
> already included (according to the 
> doc
> ).
>
> I'd like to disable as well JSP precompilation. Any idea?
>
> Thanks,
> Jordi.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/vQXBomHidrYJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Scheduler Bug - Instances Explosion

[cloudpre]

Hi - I have an app which has started to misbehave in the last 2 hours. It 
has taken over 150 instances and looping over. Generally, it's happy with 
1-2 instances.

Is anyone else having the same problem?

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Scheduler Bug (2)

[cloudpre]

Hi - I have confirmed in my two different production apps. The scheduler 
has gone into a spin and normally 1-2 instances, it has become 200-400 
instances. The app had $75/day limit and it hit it.

Does Appengine engineers test their builds before they make us the guinea 
pigs?

Thanks.

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: too many appengine frontend instances

[cloudpre]

We have two applications on AppEngine. We use F4. You can imagine the costs 
when they have gone into 450 instances. 

Any idea on how we are going to be compensated for the down time (app out 
of quota - $100/day) and the lost business?


On Friday, May 9, 2014 9:10:19 AM UTC+5:30, blackdew wrote:
>
> my server make too many Frontend instances
>
> may be it make instance per request
>
> from 2 hours ago
>
> and my last deploy was yesterday may be 24 hours ago
>
> so, help and give me any advice
>
> thanks
>

-- 
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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: HR datastore is in readonly but there are no errors?

[cloudpre]

We are also facing same issue for last 30 mins. If there are any updates 
from Google that anyone has got, please share here.

On Saturday, April 11, 2015 at 1:08:09 AM UTC+5:30, Matija wrote:
>
> Are we only one with this problem? For the last one hour it is like HR 
> datastore is in some kind read only state but datastore put statements 
> don't return any errors?
>
> We have noticed that they are testing 1.9.19 java GAE version on some 
> instances.
>
> Anybody??? What to do? Where to report? Koju posluku porati?
>

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/08a1e36a-1523-42bf-a66e-223cd6651127%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.