Issue 129 in walkaround: Error 500, Over quota

[walka...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 129 by comerc...@conductum.com: Error 500, Over quota
http://code.google.com/p/walkaround/issues/detail?id=129

What steps will reproduce the problem?
1. A low use of the app.
2.
3.

What is the expected output?
Normal access

What do you see instead?
Error 500
OVER QUOTA
Internal server error


What browser and browser version are you using? On what operating system?
Chorme on XP, last versión
Mozilla on XP, last versión
Chorme for Iphone, last versión

What URL does your browser show when the problem occurs? Did you compile
walkaround on your machine, or are you using a public instance?
Im not sure

Please provide any additional information below.
I cloned "walkaround" on 18 june 2012.
I used it daily since then.

On 09 january 2012 I updated new version.
Since then, I have overcuota errors.
I do the same use than before the update (1-2 users).

Dashboard:
Datastore Read Operations 100% 0.05 of 0.05 Million Ops


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[Chinarut Ruangchotvit]

what's the status here?   I've "tried again later" for the past week and still getting this error.

at the very least, I would like to get an export of all my waves.   Is there a way to arrange this and preserve what sounds like needed quota?

[Yuri Zelikov]

Hi

Google initially donated some free quota for wavereactor, but it's over for a couple of months now. I don't have enough resources to buy enough quota on my own.

Regarding export - I am currently checking the possibility of waves export ot alternative services, but don't expect it any time soon.

[R. Drew Davis]

What are the requirements for Wavereactor to stay in business?  e.g. $x/month at recent usage levels.   What is x?

Has Wavereactor made any notable implementation progress that makes a compelling story for why it should persist?

How does Wavereactor's progress and user base compare to the Russian incarnation of Wave (rizzoma.com)?    (I confess to a deep-seated suspicion of the privacy of the waves on that site)

[Yuri Zelikov]

See inline

On Saturday, May 25, 2013 6:17:51 PM UTC+3, R. Drew Davis wrote:

What are the requirements for Wavereactor to stay in business?  e.g. $x/month at recent usage levels.   What is x?

   5-15 $ per day (depends on load)

Has Wavereactor made any notable implementation progress that makes a compelling story for why it should persist?

   Not sure I understand your question.

How does Wavereactor's progress and user base compare to the Russian incarnation of Wave (rizzoma.com)?    (I confess to a deep-seated suspicion of the privacy of the waves on that site)

   Do you mean feature wise? Well Rizzoma has more features. But Walkaround (wavereactor is demo instance for the walkaround project) is open source and can be installed on ypur own appengine instance. 

[Chin]

thank you Drew for chiming in - I am curious (on a separate thread in regards to your concern around Rizzoma and privacy)

Yuri, $5-15/day is clear.

a few more questions:

1) when does your quota reset?

2) will it be possible to have access to a list of waves short-term with limited quota?  right now I have no visibility as to what is actually on the server - this would be a first step.

3) if you disable access to the waves themselves , how much bandwidth is required to download existing waves on the server to migrate to our own instances?

I am hoping 2 & 3 is a stopgap until a business case is built (as Drew suggests) to support the $1800-5400 you need annually just to support the bandwidth required for Wavereactor.

chinarut 

You received this message because you are subscribed to a topic in the Google Groups "walkaround-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/walkaround-dev/a9A0mERUDBg/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to walkaround-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Yuri Zelikov]

Hi

See inline

On Sunday, May 26, 2013 12:23:40 AM UTC+3, Chinarut Ruangchotvit wrote:

thank you Drew for chiming in - I am curious (on a separate thread in regards to your concern around Rizzoma and privacy)

Yuri, $5-15/day is clear.

a few more questions:

1) when does your quota reset?

       AppEngine resets the quota daily

2) will it be possible to have access to a list of waves short-term with limited quota?  right now I have no visibility as to what is actually on the server - this would be a first step.

    Yes, currently it is running on 1.5$ per day which is only enough to pay for the data stored in AppEngine DB to avoid data loss. Increasing the quota will allow to access the waves list.

3) if you disable access to the waves themselves , how much bandwidth is required to download existing waves on the server to migrate to our own instances?

    First, there's no support for waves export as for now. But it should be possible to implement with some effort. I don't know how much would it cost to export, but I think the actual price will be somewhere in 1-10 cents per wave. 

[Fermín Ortueta Izco]

Hi Yuri,

i was referring to my own walkaround clone, no to wavereactor.

Any idea about why latest version of walkaround spends "Datastore Read Operations" faster than previous versions?

Ty,

[Fermín Ortueta Izco]

I like new google group interface.

Maybe i use it like g. wave  ;)

[Yuri Zelikov]

No, but you can try to dig this mail list, I think someone already asked this question, not sure if it was answered.

[Fermín Ortueta Izco]

Do you refer my first post?

[Chinarut Ruangchotvit]

Fermin:  I'm not sure what this has to do with the issue we are experiencing with quota.

please kindly find the thread you started and reply there.  thanks!