?xml version=1.0 encoding=UTF-8?
cronentries
cron
url/long-task/url
description/description
scheduleevery 30 minutes/schedule
targetname-of-the-backend/target
/cron
/cronentries
On Oct 20, 4:16 am, fachhoch fachh...@gmail.com wrote:
I have a heavy duty servlet whihc
http://www.pdjamez.com/2011/05/google-app-engine-backends-part-deux/
On Oct 23, 5:42 pm, Peter Dev dev133...@gmail.com wrote:
?xml version=1.0 encoding=UTF-8?
cronentries
cron
url/long-task/url
description/description
scheduleevery 30 minutes/schedule
targetname
sessions-enabledtrue/sessions-enabled
App Engine stores session data in the datastore and memcache, all
values stored in the session must implement the java.io.Serializable
interface.
in java session.getAttribute(XY) calls Datastore API READ if data in
Memcache not found? (free limit
After each vote we want to send back the actual state of voted object
(actual votes)... so, we need to store the number of votes and not
only the deltas.
Actual state of the votes we could store in backends cache, and in
batch write changes in db.
What do you think about this solution?
I
Price:
- with backends lets say 3 B2 machines = 350USD/Month
- UrlFetch Data Sent/Received 0,15USD/GB
Limit:
- URL Fetch Daily Limit 46,000,000 calls
this can be a problem...but I see it is possible to request an
increase
Write data parallel in DB: Task Queue with rate
Shared counter is cool and I use it... but if you have millions of
objects I cannot imagine how to manage them.
1 000 000 obj x 100 shards = 10 000 000 counters
1. How to reset them to 0 in specified periods?
2. How to set the shared sum for each object to show top 100 objects?
3. Too much DB API
Sorry, 100 000 000 counters
On Sep 27, 4:53 pm, Peter Dev dev133...@gmail.com wrote:
Shared counter is cool and I use it... but if you have millions of
objects I cannot imagine how to manage them.1 000 000obj x 100 shards =10 000
000counters
1. How to reset them to 0 in specified periods
http://code.google.com/appengine/articles/managing-resources.html
For Java HTTP sessions, write asynchronously - HTTP sessions (Java)
lets you configure your application to asynchronously write http
session data to the datastore by adding async-session-persistence
enabled=true/ to your
We are developing an application, where users can vote for many
objects.
(for example, voting the best music video of the week)
- This means, we have millions of possible objects to vote for, and
millions of users
To our best knowledge, after taking in consideration different
options, the best
Datastore APIs new pricing - Query (FirstResult/MaxResults)
http://code.google.com/appengine/kb/postpreviewpricing.html#two_entities_fetched_operations_consumed
- one more question. Query like this:
Query query = session.createQuery(select u from User u order by
u.age);
query.setFirstResult(10);
http://code.google.com/appengine/kb/postpreviewpricing.html#two_entities_fetched_operations_consumed
*** Query like this:
Query query = session.createQuery(select u from User u order by
u.age);
query.setFirstResult(10);
query.setMaxResults(30);
= 30 read ops (first 10 skipped) or 40 read ops (GAE
11 matches
Mail list logo
