
If people find the ads that annoying, I don't mind taking them down - I just don't like taking money from people to run the site.
mr x wrote:Did I just see an add for diamonds?
That's what I understood.mr x wrote:We have the 5% bn charge on the gb's. I thought we decided that was supposed to go towards the site fees....
Sent from my Nexus 4 using Tapatalk 4
I don't know - who manages it?mr x wrote:How is our BN fund looking?
And how do we contribute to the fund?Jimmy wrote:I don't know - who manages it?mr x wrote:How is our BN fund looking?
Liam, you are correct. I'm pretty sure it pulls file.php for any attachments, smilies, avatars, etc.
It would for photos being uploaded and viewed from this point on, but any photos that are already uploaded to the site would hit file.php each time they're loaded. So while I think this would reduce executions going forward, I don't think it'll solve the problem of needing more executions per month, it'll just slow the amount of time until the next upgrade would be required.Jimmy wrote:Hosting pictures offsite should help reduce the executions (as far as I know - Jeff, Rob, correct me if I'm wrong).
Yup, any hosted file viewed will hit file.php.Jimmy wrote:Liam, you are correct. I'm pretty sure it pulls file.php for any attachments, smilies, avatars, etc.
I don't care who the site is hosted by, but wouldn't executions just be another term for resource usage? This is how they describe the executions "You have exceeded the daily Account Executions limit of your account. Exceeding the CPU Time limit means that the execution of your script(s) takes too much CPU resources."jeffsmith wrote:It would for photos being uploaded and viewed from this point on, but any photos that are already uploaded to the site would hit file.php each time they're loaded. So while I think this would reduce executions going forward, I don't think it'll solve the problem of needing more executions per month, it'll just slow the amount of time until the next upgrade would be required.Jimmy wrote:Hosting pictures offsite should help reduce the executions (as far as I know - Jeff, Rob, correct me if I'm wrong).
The whole basis of pricing on executions is quite foreign to me in the hosting world. Things are usually based on three things: resource usage, disk space, and bandwidth. I know that moving the site to a new host would be a monumental task, but it may be something that's necessary at some point to keep hosting affordable.
Not entirely—a lot of hosting companies don't have a set amount of CPU time you can use per month. What you normally have is a resource cap (memory and CPU usage) that you can't max out for an extended period of time because it affects all of the other customers that are on the same server as you.Jimmy wrote:I don't care who the site is hosted by, but wouldn't executions just be another term for resource usage? This is how they describe the executions "You have exceeded the daily Account Executions limit of your account. Exceeding the CPU Time limit means that the execution of your script(s) takes too much CPU resources."
With our current hosting plan, we have 20g of disk space and unlimited bandwidth.
Users browsing this forum: No registered users and 1 guest