Language Selection

English French German Italian Portuguese Spanish

slashdot effect

Filed under
Site News

I can only apologize for the slowness and inaccessibility of the site past coupla days and that one other occurrence last month I guess it was. I was /.'d last month and osnews'd yesterday (continuing today). I can't really do much about it right now. I subscribe to bellsouth's largest business pipe in our area, but it's still quite limited upstream. The only way I can think of to alleviate this condition is to perhaps consider off-site hosting. I don't really want to do this for several reasons, but the main one is the financial considerations. Fortunately (or unfortunately - depending upon how you look at it) this only happens once in a while, so I guess I'll (we'll?) have to just live with it for now. If this issue continues to come up, I'll look at my alternatives more closely.

Some folks have joked that my site had been taken down, and for now this hasn't been true. As my logs will testify, my server continued to function at all times, saddly I ran out of pipe. I have a fair amount of confidence in apache (and drupal) to handle large loads and hopefully we won't have to deal with that issue.

Anyway, all that to say, thanks so much for visiting my little corner of the web. It's gratifying to receive so many hits on my original work, yet it's kinda a double-edge blade, and you, the visitor, bear the brunt. I'm sorry I don't have the bandwidth to handle those large loads so no one is denied access or their visit is painfully slow. I can't thank you enough for visiting and your comments. And of course, special thanks to pclinuxonline, Slashdot, osnews, userlocal and all the others for carrying my stories.

Thank you sincerely,
Susan

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

re: /. effect [solved]

Well, two wonderful things happened since posting this blog. Number one, dot.kde.org linked to my story, so that's where a lot of the traffic this morning was coming from. However, upon getting complaints from users not being able to connect, they set links using coral cache. Oh man, why haven't I heard of that before?

It seems to be a free distributed network kinda thing. So, if I ever experience that slashdot effect again, I can employ their service. A wonderful solution.

So, thanks to dot.kde.org for picking up my story and for planting the seed of an idea to alleviate the problem in the future.

I hope I have that problem in the future. Big Grin

----
You talk the talk, but do you waddle the waddle?

More in Tux Machines

Security Leftovers

Leftovers: BSD

  • BSD Mag: Understanding Unikernels by Russell Pavlicek
    The number of tasks which lend themselves to being unikernels is larger than you might think. In 2015, Martin Lucina announced the successful creation of a “RAMP” stack. A variant of the common “LAMP” stack (Linux. Apache, MySQL, PHP/Python), the “RAMP” stack employs NGINX, MySQL, and PHP each built on Rumprun. Rumprun is an instance of a Rump kernel, which is a unikernel system based on the modular operating system functions found in the NetBSD project. So even this very common solution stack can be successfully converted into unikernels.
  • Summary of the preliminary LLDB support project
    Operating systems can be called monitors as they handle system calls from userland processes. A similar task is performed by debuggers as they implement monitors for traced applications and interpret various events that occurred in tracees and are messaged usually with signals to their tracers. During this month I have started a new Process Plugin within LLDB to incept NativeProcessNetBSD - copied from NativeProcessLinux - implementing basic functionality and handling all the needed events in the MonitorCallback() function. To achieve these tasks, I had to add a bunch of new ptrace(2) interfaces in the kernel to cover all that is required by LLDB monitors. The current Process Plugin for NetBSD is capable to start a process, catch all the needed events correctly and if applicable resume or step the process.
  • NetBSD Making Progress On LLDB Debugger Support
    NetBSD developers have been implementing the relevant interfaces needed for the LLVM debugger to effectively monitor and work on the operating system. As part of that they have also improved some of their own documentation, provided new ptrace interfaces, and more. Those interested in LLDB and/or NetBSD can learn more about this debugging work via this NetBSD.org blog post.

Firefox 51 Released With FLAC Audio Support, WebGL 2.0 By Default

Firefox 51.0 just hit Mozilla's FTP servers for those wanting the latest version of this open-source web-browser. Firefox 51 isn't a big feature release for end-users but notably does have support for FLAC audio, at long last! Great to see the web browsers finally shipping support out-of-the-box for this open-source audio codec. Read more

Intel Core i3 7100 Kabylake Linux Benchmarks

Last week I began delivering Linux Kabylake benchmarks with the Core i5 7600K while this week I finally am set to receive the Core i7 7700K. But for those curious how Kabylake is looking on the low-end, I picked up a Core i3 7100 as currently the cheapest Kabylake desktop processor. Here are some initial Linux benchmarks of this Core i3 processor on Ubuntu Linux. Read more