I thought one thing and I said something completely differente -.-' I meant having a model, with the same key_id/key_name as the post and a list of users (say 4000/4500). When that super-start with 200.000 followers post something, run a taskqueue and save several models with the info. Then, for listing, do a key-only query where the user is in the list of affected ones. Then, with the keys, obtaing the posts (they have the same key_id/key_name). A cron job will delete old notifications.
Most of users will have less than 700/800 followers (if it's something like Twitter), so they will consume only one notification model per post. And the costs come from indexes (a lot of lists to index), serialization (4000/4500 items), deserialization (we use it with keys, so almost no cost), deleting old notifications (we use keys too) Anyway, I'm willing to hear new ideas, surely they can largely improve my system Ernesto -- 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/-/fC_ZvMvF6MoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
