Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jsperf.com: 503 Service Temporarily Unavailable #18

Closed
Daniel-Hug opened this issue Jun 12, 2015 · 63 comments
Closed

jsperf.com: 503 Service Temporarily Unavailable #18

Daniel-Hug opened this issue Jun 12, 2015 · 63 comments
Labels

Comments

@Daniel-Hug
Copy link

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Apache/2.2.22 (Debian) Server at jsperf.com Port 80

@burnaDLX
Copy link

Now the complete site seems down. When you enter the page just a 'Website Disabled' appears.

@arthurvr
Copy link

Yep, I'm able to confirm that. @mathiasbynens something up with the server?

@jdalton jdalton added the bug label Jun 19, 2015
@mathiasbynens
Copy link
Contributor

Yeah. Due to the ongoing flood of spam, the database has gotten so big any type of query takes ages, effectively bringing down the server. Unfortunately I don’t have time to deal with this right now.

The new version is gonna need some sort of authentication before posting test cases/comments, e.g. GitHub Authentication.


What you can do to help

Fix the open issues in this repository, especially the ones blocking the v2 release.

Things that don’t help in any way

Posting +1 comments to this thread.


Thanks for understanding.

@tomByrer
Copy link

Couldn't you just lock out new postings for now, & delete the last few days/weeks if they're that spammy?
There are alot of bookmarks out there, esp StackOverflow...

@mbrevda
Copy link

mbrevda commented Jun 22, 2015

+1 for a read only mode. It isn't ideal, but its better than nothing...

@x3cion
Copy link

x3cion commented Jun 22, 2015

+1 for at least read only.

... this breaks half of stackoverflow!

@matt-curtis
Copy link

+1 for read only mode!

3 similar comments
@gcorreaalves
Copy link

+1 for read only mode!

@lucasklaassen
Copy link

+1 for read only mode!

@EricDunaway
Copy link

+1 for read only mode!

@dmitrymatveev
Copy link

+1 read only !!!

@josephrocca
Copy link

+1!

@fresheneesz
Copy link

Image of Yaktocat

+1

@minecrawler
Copy link

+1 Read only mode

@JuhQ
Copy link

JuhQ commented Jun 23, 2015

+1 For read only mode!

1 similar comment
@ghost
Copy link

ghost commented Jun 23, 2015

+1 For read only mode!

@mfpopa
Copy link

mfpopa commented Jun 23, 2015

Another +1 for read only mode. Thanks.

@QuakePhil
Copy link

+1 for read only

@nduvieilh
Copy link

+1 For read only mode!

@pedroassis
Copy link

+1

@BridgeAR
Copy link

+1

@jeremysawesome
Copy link

👍 Readonly

@diegofurtados
Copy link

+1

@stri8ed
Copy link

stri8ed commented Jun 23, 2015

+1 Read-only

1 similar comment
@DekusDenial
Copy link

+1 Read-only

@nhz-io
Copy link

nhz-io commented Jun 24, 2015

@JonDum we are building up momentum right now. We all highly depend on jsperf anyway, so the action WILL BE TAKEN!
P.S.
I am going to try to implement gist based storage this weekend along with the sandbox.

@S-YOU
Copy link

S-YOU commented Jun 24, 2015

I think, comments don't have to support out of the box.

@jlukic
Copy link

jlukic commented Jun 24, 2015

Thanks @mathiasbynens for all your work in keeping JsPerf up, its an amazing resource for the community. Please let us know if you have any specific recommendations on how we can help out.

@nhz-io
Copy link

nhz-io commented Jun 24, 2015

Sent an email to stackexchange asking for help, lets see where it goes.

@jczimm
Copy link

jczimm commented Jun 24, 2015

+1 for read only mode

@nhz-io
Copy link

nhz-io commented Jun 24, 2015

mail went to openshift, heroku and digital ocean, lets see if anyone cares.

@haneytron
Copy link

@mathiasbynens this has definitely KO'd some Stack Overflow answers. A question: if we provided a list of jsperf URLs, would you be able to return a set of raw HTML/CSS/JS for each link? We might be able to run an update to insert our own Stack Snippets where each JSPerf link was, which would improve the SO answers. No promises that we'll do it - just probing options. Please let me know. Cheers!

@andrewsomething
Copy link

DigitalOcean would be happy to help provide some resources to keep jsPerf up and running! @mathiasbynens if you're interested, please reach out via opensource@digitalocean.com so we can discuss your requirement and how we can help.

@nhz-io
Copy link

nhz-io commented Jun 24, 2015

Oh yeah! There is some GOOD left in the world!

@haneytron
Copy link

@mathiasbynens cc @nhz-io jsperf restoring your hosting capabilities and bringing the site back online is a much better solution than us band-aiding the questions and answers, which ultimately will take away from some of your traffic anyway since we'd be replacing the links. I'd prefer you restore service if possible, but please let me know if service cannot be restored / you're down for good.

@dknecht
Copy link

dknecht commented Jun 24, 2015

Cloudflare is happy to sponsor this project. Please email me (dane at cloudflare dot com) and we can discuss how to get better protections in place.

@MadaraUchiha
Copy link

How does one help with the issues blocking the v2 milestone? The tickets' descriptions are basically a link to another repository.

@RaphaelDDL
Copy link

@MadaraUchiha The 'another repository' is the v2 one. @maxbeatty is the one in charge of the refactoring. You can help him.

@josephrocca
Copy link

As a temporary solution it looks like you can add "cache:" in front of a
jsperf url to get the google cached version and it all works fine

On Thu, Jun 25, 2015 at 6:00 AM, Raphael DDL Oliveira <
notifications@github.com> wrote:

@MadaraUchiha https://github.com/MadaraUchiha The 'another repository'
is the v2 one. @maxbeatty https://github.com/maxbeatty is the one in
charge of the refactoring. You can help him.


Reply to this email directly or view it on GitHub
#18 (comment).

@gobwas
Copy link

gobwas commented Jun 25, 2015

Do you plannin, since it will be github auth, to keep tests in gists? For example, save test case to gist, and load test case from gist?

@mathiasbynens
Copy link
Contributor

Do you plannin, since it will be github auth, to keep tests in gists? For example, save test case to gist, and load test case from gist?

No changes are planned compared to the original jsPerf website (other than requiring GitHub authentication to be able to post tests/comments). Maybe later.

@nhz-io
Copy link

nhz-io commented Jun 25, 2015

@gowab yes, but not in v2, its a nice idea but for now priority is to bring jsperf back to life

@gobwas
Copy link

gobwas commented Jun 25, 2015

@mathiasbynens @nhz-io sounds good. If you need some help - ping me )

@ffigiel
Copy link

ffigiel commented Jun 25, 2015

+1

@mathiasbynens
Copy link
Contributor

Thanks for reaching out, Cloudflare (@dknecht) and DigitalOcean (@andrewsomething)! You’ve got email.

@hccampos
Copy link

Glad to see that Cloudflare and DigitalOcean are willing to help out. Kudos!

@abacaj
Copy link

abacaj commented Jun 26, 2015

jsperf is dead?

@vasiliy0s
Copy link

+1 for read-only

@vairix-dmacchi
Copy link

+1 for read only mode!

@arthurvr
Copy link

Things that don’t help in any way

Posting +1 comments to this thread.

@BobbyWibowo
Copy link

+1

EDIT: Hah!

@jsperf jsperf locked and limited conversation to collaborators Jun 26, 2015
@mathiasbynens
Copy link
Contributor

I’ve temporarily re-enabled jsPerf with Google reCAPTCHA implemented. Let’s see how this goes.

@mathiasbynens
Copy link
Contributor

Somehow spam still started getting through after a while, indicating this is in fact manual spam (unless someone managed to break Google ReCaptcha already, which I highly doubt).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests