Cookbooks - Chef Supermarket - Downloads counter


#1

Hi All,

does anyone know how works the number of downloads counter in the
supermaket cookbook?

Just to be clear, I have published few days ago an this empty cookbook:

https://supermarket.chef.io/cookbooks/empty

now I see about 30k downloads (and counting), which are a little bit too
many for an empty cookbook, isn’t it?


#2

On Jan 18, 2015, at 6:58 PM, Vincenzo D’Amore v.damore@gmail.com wrote:

does anyone know how works the number of downloads counter in the supermaket cookbook?

Just to be clear, I have published few days ago an this empty cookbook:

https://supermarket.chef.io/cookbooks/empty

now I see about 30k downloads (and counting), which are a little bit too many for an empty cookbook, isn’t it?

I think it’s because every time Berkshelf hits the /universe endpoint to resolve dependencies, it increments the access count of all cookbooks.

  • Julian

#3

Kinda, but not really.

I should write a blog post about this but the TL;DR is that older berkshelf-api servers had to download every cookbook to build the /universe endpoint. They, by default, did this every 5 mins.

I will try and get a post together next week with more details. I do want to make it clear that, until supermarket was released, downloading every cookbook was the only way to get the data needed to build the /universe endpoint.

Thanks!

– cwebber

On Jan 18, 2015, at 17:08, Julian C. Dunn jdunn@aquezada.com wrote:

On Jan 18, 2015, at 6:58 PM, Vincenzo D’Amore v.damore@gmail.com wrote:

does anyone know how works the number of downloads counter in the supermaket cookbook?

Just to be clear, I have published few days ago an this empty cookbook:

https://supermarket.chef.io/cookbooks/empty

now I see about 30k downloads (and counting), which are a little bit too many for an empty cookbook, isn’t it?

I think it’s because every time Berkshelf hits the /universe endpoint to resolve dependencies, it increments the access count of all cookbooks.

  • Julian

#4

On Jan 18, 2015, at 5:08 PM, Julian C. Dunn jdunn@aquezada.com wrote:

On Jan 18, 2015, at 6:58 PM, Vincenzo D’Amore v.damore@gmail.com wrote:

does anyone know how works the number of downloads counter in the supermaket cookbook?

Just to be clear, I have published few days ago an this empty cookbook:

https://supermarket.chef.io/cookbooks/empty

now I see about 30k downloads (and counting), which are a little bit too many for an empty cookbook, isn’t it?

I think it’s because every time Berkshelf hits the /universe endpoint to resolve dependencies, it increments the access count of all cookbooks.

Yep, also search bots and a lot of other things, but berks-api was the final nail in the coffin.

–Noah


#5

In about two weeks an empty cookbook
https://supermarket.chef.io/cookbooks/empty have around 224,000 downloads
I definitely think there is something wrong in the download counter.

On Mon, Jan 19, 2015 at 3:17 AM, Noah Kantrowitz noah@coderanger.net
wrote:

On Jan 18, 2015, at 5:08 PM, Julian C. Dunn jdunn@aquezada.com wrote:

On Jan 18, 2015, at 6:58 PM, Vincenzo D’Amore v.damore@gmail.com
wrote:

does anyone know how works the number of downloads counter in the
supermaket cookbook?

Just to be clear, I have published few days ago an this empty cookbook:

https://supermarket.chef.io/cookbooks/empty

now I see about 30k downloads (and counting), which are a little bit
too many for an empty cookbook, isn’t it?

I think it’s because every time Berkshelf hits the /universe endpoint to
resolve dependencies, it increments the access count of all cookbooks.

Yep, also search bots and a lot of other things, but berks-api was the
final nail in the coffin.

–Noah


Vincenzo D’Amore
email: v.damore@gmail.com
skype: free.dev
mobile: +39 349 8513251


#6

I actually wrote about this recently and my response to the original never posted to the list because, apparently, email is hard.

https://www.chef.io/blog/2015/01/21/those-pesky-supermarket-download-counts/ https://www.chef.io/blog/2015/01/21/those-pesky-supermarket-download-counts/ is the post you will want to go take a look at.

Thanks!

— cwebber

On Feb 2, 2015, at 8:31 AM, Vincenzo D’Amore v.damore@gmail.com wrote:

In about two weeks an empty cookbook https://supermarket.chef.io/cookbooks/empty have around 224,000 downloads
I definitely think there is something wrong in the download counter.

On Mon, Jan 19, 2015 at 3:17 AM, Noah Kantrowitz <noah@coderanger.net mailto:noah@coderanger.net> wrote:

On Jan 18, 2015, at 5:08 PM, Julian C. Dunn <jdunn@aquezada.com mailto:jdunn@aquezada.com> wrote:

On Jan 18, 2015, at 6:58 PM, Vincenzo D’Amore <v.damore@gmail.com mailto:v.damore@gmail.com> wrote:

does anyone know how works the number of downloads counter in the supermaket cookbook?

Just to be clear, I have published few days ago an this empty cookbook:

https://supermarket.chef.io/cookbooks/empty https://supermarket.chef.io/cookbooks/empty

now I see about 30k downloads (and counting), which are a little bit too many for an empty cookbook, isn’t it?

I think it’s because every time Berkshelf hits the /universe endpoint to resolve dependencies, it increments the access count of all cookbooks.

Yep, also search bots and a lot of other things, but berks-api was the final nail in the coffin.

–Noah


Vincenzo D’Amore
email: v.damore@gmail.com mailto:v.damore@gmail.com
skype: free.dev
mobile: +39 349 8513251 tel:%2B39%20349%208513251


#7

Christopher Webber wrote:

I actually wrote about this recently and my response to the original never posted to the list because, apparently, email is hard.

Not only did your informative response of January 18 which explained
what is happening with the download counter get posted to the list and
distributed to subscribers (to me, at least), but Vincenzo quoted your
response
(and Julian’s, and Noah’s) in his followup post today.

This list might benefit from an FAQ and a welcome message for newbies.
E-mail is not hard. We solved most if not all of the communications
problems seen regularly on this list decades ago on other mailing lists
and on Usenet newsgroups. There are good reasons for providing
informative subject headers, asking questions “the smart way”, trimming
your posts, and refraining from TOFU quoting.


Phil Mocek
https://mocek.org


#8

I actually wrote about this recently and my response to the original never
posted to the list because, apparently, email is hard.

https://www.chef.io/blog/2015/01/21/those-pesky-supermarket-download-counts/ is
the post you will want to go take a look at.

Thanks Christopher for your answer, nevertheless this counter is
misleading, something should be done.
If someone doesn’t know the story behind the download counter, for sure
think: this cookbook should be almost perfect, if there are so many
downloads.
I spent 2 days before I understood that a cookbook with about 16 million
downloads
was heavily bugged.
Instead to wait that berkshelf-api servers to run more efficiently, the
rules behind that download counter should change.
May be split the number of download done by a person from the number of
automatic downloads (HTTP User Agents).


#9

Feel free to file an issue here:


instead of moaning about it on the mailing list.

cheers,

–aj

On Wed, Feb 4, 2015 at 12:48 PM, Vincenzo D’Amore v.damore@gmail.com
wrote:

I actually wrote about this recently and my response to the original
never posted to the list because, apparently, email is hard.

https://www.chef.io/blog/2015/01/21/those-pesky-supermarket-download-counts/ is
the post you will want to go take a look at.

Thanks Christopher for your answer, nevertheless this counter is
misleading, something should be done.
If someone doesn’t know the story behind the download counter, for sure
think: this cookbook should be almost perfect, if there are so many
downloads.
I spent 2 days before I understood that a cookbook with about 16 million
downloads
was heavily bugged.
Instead to wait that berkshelf-api servers to run more efficiently, the
rules behind that download counter should change.
May be split the number of download done by a person from the number of
automatic downloads (HTTP User Agents).