Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
The generate content scripts are fantastic. Many people who generate content will want to run tools like siege against the content, taxonomy pages, feeds, user pages.
Could we generate a list of URL's for all the content we create?
Kieran
Comments
Comment #1
moshe weitzman CreditAttribution: moshe weitzman commentedAnyone want to take this on?
Comment #2
jamesJonas CreditAttribution: jamesJonas commentedHere is a very simple program to create a urls.txt file for 'siege'. Not fancy, but gets the job done.
$domain_name = the domain name you are testing
$min_node = the first node in your site
$max_node = the last node in your site
$number of urls = the number of urls you wish to create.
$subdir = the subdirectory in you site
This is designed to run from command line. If you wish to add several different types of content then run it several times changing
$fh=fopen("/usr/etc/urls.txt","a");
$subdir = "/node/"; to some other content
Running siege
James
Comment #3
joshk CreditAttribution: joshk commentedFYI I'll be working on this:
http://drupal.org/project/siege
Comment #4
joshk CreditAttribution: joshk commentedAlso, for people interested in getting real-world data for Siege purposes, Sproxy is a great resource:
http://www.joedog.org/Sproxy/Manual
Comment #5
federico CreditAttribution: federico commentedYou can take an urllist from xmlsitemap.
Just: copu everything, paste into a spreadsheet editor and divide columns (text to columns) . Copy the first column to a text editor.
Comment #6
federico CreditAttribution: federico commentedYou can take an url list from xmlsitemap module.
Just: copy everything in yoursite/sitemap.xml , paste into a spreadsheet editor and divide columns (text to columns) . Copy the first column to a text editor.
Comment #7
devyd CreditAttribution: devyd commentedFor the record:
If not obvious, sproxy will be tunneling your browser requests.
That means, as a result, the urls.txt will include all .js, .css, favicon.ico etc. request data from a real browser -- exactly what you need.
As joshk mentioned, it won't get any more realistic than this. Think: "unprimed cache frontpage hit"-urls.txt file.
A great solution. I don't see the need for a module support here -- anyone who is using siege for his work ... should also be able to do a quick installation of sproxy, imho.
Comment #8
salvisThanks, devyd!