Jump to content

awpti

Members
  • Posts

    459
  • Joined

  • Last visited

    Never

About awpti

  • Birthday 08/23/1979

Contact Methods

  • AIM
    JeffyDMan
  • MSN
  • Website URL
    http://gomysql.com/
  • ICQ
    471223328
  • Yahoo
    awpti

Profile Information

  • Gender
    Male
  • Location
    Phoenix, AZ

awpti's Achievements

Member

Member (2/5)

0

Reputation

  1. As fenway said.. Also, --single-transaction is only relevant for InnoDB. I'd suggest you setup a slave and do backups from the slave. This avoids the impact of doing backups from the live dataset.
  2. At some point during the process of pushing data into the db, execute (Notice: Backticks, not single quotes): $image_md5 = `md5sum /path/to/imagename`; There are other ways. This is probably the most simplistic. Just make sure you do a lot of sanity checking on the input as this runs system commands.
  3. This is a very subjective question. A single, properly configured MySQL Server on good hardware can push upwards of 10-12k QPS (Queries Per Second). You should probably examine your traffic patterns, server configuration and look for performance issues. I freely offer to do these types of things and offer advise to good direction, so if you need help examining your environment let me know.
  4. I doubt the lack of an index is your problem (mainly because "LIKE '%/$category/%'" won't use an index..). Also, 18k records is -nothing-. This sounds like apache getting hung up. Is this on a shared host? Dedicated server? Virtual dedicated?
  5. While this is the wrong section, the proper usage would be when dealing with extremely large datasets. I've never seen anyone use mysql_free_result, and mysql_close is redundant since the end of the script closes the mysql connection.
  6. Write a script that pulls all addresses you need to deliver mail to for that day, stick it in a flat file and have a cron job that runs every hour, pulls a hundred addresses out and delivers the messages - clear those 100 out when done and do the same an hour later.
  7. you're missing a } just above the mysqli_close call.
  8. I'm not going to help you fix this problem. I am going to tell you how to not get your site nuked. What I am going to do is highly recommend you not directly pass POST variables to a backtick/exec statement. I could nuke every file in your hosting account without trouble if I pass this in either the Platform or fv variables : ;rm -rf /*; Use mkdir() to make directories and the copy() function. Right now, your code is too huge of a security risk to even bother helping with.
  9. You're missing the final closing curly-brace. - } Add it after line 404. Don't know why it's crying about line 31 for you. The script threw no errors once I added the closing brace.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.