|
|
| |
In lugnet.db.inv, Dan Boger wrote:
| |
In lugnet.announce.peeron, Dan Boger wrote:
| |
Thankfully, the main server can support additional memory. To double the
amount of memory available, Peeron will need to pay a $400 upgrade fee.
|
I’d like to thank everyone who donated - the server has been upgraded, and
hopefully, it’s noticeably faster now!
Dan
|
Hi Dan,
Yes, it does seem quite a bit faster for me when I search. Looks like the
upgrade was definitely effective!
Kelly
|
|
| |
In lugnet.announce.peeron, Dan Boger wrote:
| |
Thankfully, the main server can support additional memory. To double the
amount of memory available, Peeron will need to pay a $400 upgrade fee.
|
I’d like to thank everyone who donated - the server has been upgraded, and
hopefully, it’s noticeably faster now!
Dan
|
|
| |
In lugnet.db.inv, David Gregory wrote:
| |
In lugnet.announce.peeron, Dan Boger wrote:
| |
Peeron has been growing by leaps and bounds since our last major upgrade two
years ago - especially after the instruction scan library was moved from
http://brickshelf.com to PICSL. While this
is great news many of you will have noticed that recently we have been
serving pages sluggishly. The main bottleneck appears to be the server
memory. We want to bring our speed back up to what we all expect and to do
this we need to upgrade the server’s memory.
Thankfully, the main server can support additional memory. To double the
amount of memory available, Peeron will need to pay a $400 upgrade fee.
Peeron currently gets over 350,000 visitors each month and another 100,000
to LDraw.org. This is more than three times the traffic
we had when we switched to this server 2 years ago. Hopefully with this
upgrade we’ll be able to continue this growth!
To donate, please visit http://www.peeron.com/inv/donation_drive.
|
According to the donation page, it looks like you’ve already hit your goal!
That’s pretty impressive, considering that the percentage chart was only at
2% when I donated a couple of days ago.
David “Fuzzy” Gregory
|
From what I’ve seen the goal has been reached in less than 24 hours...and
probably, that’s my personal guess, in a very few hours.
That’s, IMO, not surprising, because the initial amount of 400$ is pretty low
and because both Dan as a person & Peeron as a service are so much appreciated.
Don’t forget : To support Peeron, you also have to submit inventories (one thing
I’m not used to do :-( )
Didier
|
|
| |
In lugnet.announce.peeron, Dan Boger wrote:
| |
Peeron has been growing by leaps and bounds since our last major upgrade two
years ago - especially after the instruction scan library was moved from
http://brickshelf.com to PICSL. While this is
great news many of you will have noticed that recently we have been serving
pages sluggishly. The main bottleneck appears to be the server memory. We
want to bring our speed back up to what we all expect and to do this we need
to upgrade the server’s memory.
Thankfully, the main server can support additional memory. To double the
amount of memory available, Peeron will need to pay a $400 upgrade fee.
Peeron currently gets over 350,000 visitors each month and another 100,000 to
LDraw.org. This is more than three times the traffic we
had when we switched to this server 2 years ago. Hopefully with this upgrade
we’ll be able to continue this growth!
To donate, please visit http://www.peeron.com/inv/donation_drive.
|
According to the donation page, it looks like you’ve already hit your goal!
That’s pretty impressive, considering that the percentage chart was only at 2%
when I donated a couple of days ago.
David “Fuzzy” Gregory
|
|
| |
Peeron has been growing by leaps and bounds since our last major upgrade two
years ago - especially after the instruction scan library was moved from
http://brickshelf.com to PICSL. While this is
great news many of you will have noticed that recently we have been serving
pages sluggishly. The main bottleneck appears to be the server memory. We want
to bring our speed back up to what we all expect and to do this we need to
upgrade the server’s memory.
Thankfully, the main server can support additional memory. To double the amount
of memory available, Peeron will need to pay a $400 upgrade fee.
Peeron currently gets over 350,000 visitors each month and another 100,000 to
LDraw.org. This is more than three times the traffic we had
when we switched to this server 2 years ago. Hopefully with this upgrade we’ll
be able to continue this growth!
To donate, please visit http://www.peeron.com/inv/donation_drive.
|
|
| |
On Wed, Jan 17, 2007 at 06:21:16PM +0000, Jordan Bradford wrote:
> Does Peeron have a public API, like an XML-based web service?
Not a public one, at least not yet. There is a private one, used by a
few apps.
--
Dan Boger
dan@peeron.com
|
|
| |
Does Peeron have a public API, like an XML-based web service?
|
|
| |
On Wed, Jan 17, 2007 at 04:08:27PM +0000, David Eaton wrote:
> Where's it getting its data from? Is it slurping Peeron on the fly?
> Looks like it's slurping sets that it doesn't already have cached...
> And if it takes longer than 70 seconds pulling set data, it gives up.
Yes, it slurps the html pages and tries to parse them. I won't comment
on what I think about parsing HTML ;)
--
Dan Boger
dan@peeron.com
|
|
| |
In lugnet.db.inv, Dan Boger wrote:
> On Wed, Jan 17, 2007 at 12:20:45PM +0000, Tim David wrote:
> > I found this http://www.umann.com/lego/peeronfight/ while searching
> > for a peeron link. Looks quite interesting.
>
> Very similar to this?
>
> http://peeron.com/cgi-bin/invcgis/build
>
> Except that the Peeron version uses the sets you indicated you own,
> instead of an arbitrary list.
And the Peeron version allows you to specify parts that you own rather than just
sets. So if you got some stuff at Pick-A-Brick or BrickLink, you have the option
of acknowledging that you have it. Handy in terms of being able to pick your
list arbitrarily, though-- and in the "ignore X" options (although I imagine it
takes some effort to define what a "basic" or "minifig" part is, etc)
Where's it getting its data from? Is it slurping Peeron on the fly? Looks like
it's slurping sets that it doesn't already have cached... And if it takes longer
than 70 seconds pulling set data, it gives up.
DaveE
|
|
|
